How to connect Instantly and WhatConverts
Create a New Scenario to Connect Instantly 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 Instantly, triggered by another scenario, or executed manually (for testing purposes). In most cases, Instantly or WhatConverts will be your first step. To do this, click "Choose an app," find Instantly or WhatConverts, and select the appropriate trigger to start the scenario.

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

Instantly
Configure the Instantly
Click on the Instantly node to configure it. You can modify the Instantly 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 Instantly node, select WhatConverts from the list of available apps, and choose the action you need from the list of nodes within WhatConverts.

Instantly
โ

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 Instantly 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 Instantly 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
โ
Instantly
โ
โ
Iterator
โ
Webhook response

Save and Activate the Scenario
After configuring Instantly, 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 Instantly and WhatConverts integration works as expected. Depending on your setup, data should flow between Instantly 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 Instantly and WhatConverts
Instantly + WhatConverts + Google Sheets: When a new lead is captured in Instantly, it is created in WhatConverts. Then, the lead details are added as a new row in Google Sheets for tracking and analysis.
WhatConverts + Instantly + Slack: When WhatConverts captures a new lead, it searches for the lead in Instantly. If the lead is found, a message is sent to a Slack channel to notify the sales team of a new lead from the Instantly campaign.
Instantly and WhatConverts integration alternatives
About Instantly
Use Instantly in Latenode to automate email outreach at scale. Connect Instantly to your CRM, database, or lead sources and build automated sequences based on triggers. Enrich data and route responses using Latenode's visual editor and JS node for custom logic โ all without per-step pricing limits.
Similar apps
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 Instantly and WhatConverts
How can I connect my Instantly account to WhatConverts using Latenode?
To connect your Instantly account to WhatConverts on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Instantly and click on "Connect".
- Authenticate your Instantly and WhatConverts accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I track Instantly leads in WhatConverts?
Yes, easily! Latenode's visual editor simplifies mapping Instantly lead data to WhatConverts, ensuring accurate tracking and enhanced reporting without manual data entry. Save time and improve insights.
What types of tasks can I perform by integrating Instantly with WhatConverts?
Integrating Instantly with WhatConverts allows you to perform various tasks, including:
- Automatically creating WhatConverts leads from new Instantly prospects.
- Updating WhatConverts data when Instantly prospect status changes.
- Triggering follow-up actions in Instantly based on WhatConverts milestones.
- Enriching WhatConverts lead data with Instantly profile information.
- Generating reports combining Instantly outreach and WhatConverts conversions.
How secure is my Instantly data inside Latenode?
Latenode uses advanced encryption and security protocols to protect your Instantly data. Your credentials are never stored in plain text.
Are there any limitations to the Instantly and WhatConverts integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Instantly and WhatConverts APIs may affect high-volume workflows.
- Custom fields in Instantly and WhatConverts require careful mapping in Latenode.
- Real-time data synchronization depends on the responsiveness of both APIs.