How to connect Loyverse and WhatConverts
Create a New Scenario to Connect Loyverse and WhatConverts
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Loyverse, triggered by another scenario, or executed manually (for testing purposes). In most cases, Loyverse or WhatConverts will be your first step. To do this, click "Choose an app," find Loyverse or WhatConverts, and select the appropriate trigger to start the scenario.

Add the Loyverse Node
Select the Loyverse node from the app selection panel on the right.


Loyverse

Configure the Loyverse
Click on the Loyverse node to configure it. You can modify the Loyverse URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the WhatConverts Node
Next, click the plus (+) icon on the Loyverse node, select WhatConverts from the list of available apps, and choose the action you need from the list of nodes within WhatConverts.


Loyverse
⚙

WhatConverts


Authenticate WhatConverts
Now, click the WhatConverts node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your WhatConverts settings. Authentication allows you to use WhatConverts through Latenode.
Configure the Loyverse and WhatConverts Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Loyverse and WhatConverts Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙

WhatConverts
Trigger on Webhook
⚙

Loyverse
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Loyverse, WhatConverts, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Loyverse and WhatConverts integration works as expected. Depending on your setup, data should flow between Loyverse and WhatConverts (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Loyverse and WhatConverts
WhatConverts + Loyverse + Google Sheets: When a new lead is captured in WhatConverts, this flow checks if that lead has made a purchase in Loyverse. If a purchase is found, the lead's information along with their purchase details are added to a Google Sheet for marketing campaign analysis.
WhatConverts + Loyverse + Slack: When WhatConverts tracks a new lead, the flow verifies if the lead is an existing customer in Loyverse by searching for their contact information. If the lead is a customer, a notification is sent to a designated Slack channel, informing the sales team to personalize their follow-up.
Loyverse and WhatConverts integration alternatives

About Loyverse
Sync Loyverse sales data to your accounting or marketing tools using Latenode. Automate inventory updates based on Loyverse transactions. Trigger custom workflows for customer loyalty programs. Latenode lets you connect Loyverse data to any app without code, adding powerful automation to your POS system.
Related categories

About WhatConverts
Capture and analyze marketing leads in WhatConverts, then pipe data to Latenode to automate follow-ups. Qualify leads based on source & behavior using Latenode's no-code tools, triggering custom CRM updates or personalized email sequences. Scale lead management without complex coding.
Related categories
See how Latenode works
FAQ Loyverse and WhatConverts
How can I connect my Loyverse account to WhatConverts using Latenode?
To connect your Loyverse account to WhatConverts on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Loyverse and click on "Connect".
- Authenticate your Loyverse and WhatConverts accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I track Loyverse sales against marketing campaigns?
Yes, you can! Latenode's flexible data mapping lets you link Loyverse sales data to WhatConverts lead sources, providing ROI insights you can't get natively. Optimize marketing spend using real sales data.
What types of tasks can I perform by integrating Loyverse with WhatConverts?
Integrating Loyverse with WhatConverts allows you to perform various tasks, including:
- Track online orders in Loyverse as conversions in WhatConverts.
- Send Loyverse customer data to WhatConverts for enriched lead profiles.
- Trigger follow-up actions in WhatConverts based on Loyverse purchase history.
- Automatically update lead information in WhatConverts with Loyverse data.
- Create reports combining Loyverse sales figures and WhatConverts marketing data.
How can I filter Loyverse data before sending it to WhatConverts?
Latenode lets you use no-code filters, JavaScript functions, and AI to transform and filter Loyverse data ensuring only relevant information updates your WhatConverts account.
Are there any limitations to the Loyverse and WhatConverts integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Historical data transfer might require manual setup due to API limits.
- Complex data transformations may necessitate JavaScript coding.
- The number of tasks is limited by your Latenode subscription plan.