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

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

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

Landbot.io
⚙

SendPulse

Authenticate SendPulse
Now, click the SendPulse node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your SendPulse settings. Authentication allows you to use SendPulse through Latenode.
Configure the Landbot.io and SendPulse 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 Landbot.io and SendPulse 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
⚙

SendPulse
Trigger on Webhook
⚙
Landbot.io
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Landbot.io, SendPulse, 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 Landbot.io and SendPulse integration works as expected. Depending on your setup, data should flow between Landbot.io and SendPulse (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Landbot.io and SendPulse
Landbot.io + SendPulse + Google Sheets: When a new response is submitted in Landbot, the contact's email is added to a SendPulse mailing list, and the full response data is saved in a Google Sheet.
SendPulse + Landbot.io + Slack: When a new subscriber is added to SendPulse, a welcome message is sent to the subscriber via Landbot, and a notification is sent to a designated Slack channel to alert the marketing team.
Landbot.io and SendPulse integration alternatives
About Landbot.io
Use Landbot.io in Latenode to build no-code chatbots, then connect them to your wider automation. Capture leads, qualify prospects, or provide instant support and trigger follow-up actions directly in your CRM, databases, or marketing tools. Latenode handles complex logic, scaling, and integrations without per-step fees.
Similar apps
Related categories

About SendPulse
Use SendPulse in Latenode for automated email & SMS marketing. Trigger campaigns based on real-time events, segment contacts dynamically, and personalize messages using data from any app. Automate list cleaning and optimize send times in response to user behavior. Connect SendPulse to any data source for smarter, event-driven communication workflows.
Similar apps
Related categories
See how Latenode works
FAQ Landbot.io and SendPulse
How can I connect my Landbot.io account to SendPulse using Latenode?
To connect your Landbot.io account to SendPulse on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Landbot.io and click on "Connect".
- Authenticate your Landbot.io and SendPulse accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically add Landbot.io respondents to SendPulse mailing lists?
Yes, you can! Latenode’s visual editor makes it easy. Automatically add new Landbot.io leads to your SendPulse lists, enabling immediate, targeted email marketing and boosting engagement.
What types of tasks can I perform by integrating Landbot.io with SendPulse?
Integrating Landbot.io with SendPulse allows you to perform various tasks, including:
- Adding new Landbot.io respondents as subscribers in SendPulse.
- Sending personalized email campaigns based on Landbot.io chatbot interactions.
- Updating subscriber information in SendPulse based on Landbot.io form submissions.
- Segmenting SendPulse email lists using data collected through Landbot.io.
- Triggering automated SendPulse email sequences after Landbot.io chatbot events.
HowsecureistheLandbot.iointegrationwithSendPulseonLatenode?
Latenode uses secure authentication protocols to protect your data during Landbot.io and SendPulse integration, ensuring privacy and data integrity.
Are there any limitations to the Landbot.io and SendPulse integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex Landbot.io chatbot flows might require advanced logic configuration.
- Rate limits apply based on your Landbot.io and SendPulse subscription plans.
- Real-time data synchronization depends on API availability and network conditions.