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

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

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

Close CRM
⚙
Landbot.io
Authenticate Landbot.io
Now, click the Landbot.io node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Landbot.io settings. Authentication allows you to use Landbot.io through Latenode.
Configure the Close CRM and Landbot.io 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 Close CRM and Landbot.io 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
⚙
Landbot.io
Trigger on Webhook
⚙
Close CRM
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Close CRM, Landbot.io, 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 Close CRM and Landbot.io integration works as expected. Depending on your setup, data should flow between Close CRM and Landbot.io (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Close CRM and Landbot.io
Landbot.io + Close CRM + Slack: When a new lead is captured via Landbot, a new lead is created in Close CRM. A notification is then sent to a designated Slack channel to alert the sales team.
Landbot.io + Google Sheets + Close CRM: When a new lead is captured via Landbot, the responses are stored in a Google Sheet. The contact data is then used to update the corresponding lead in Close CRM, or create a new one if it doesn't exist.
Close CRM and Landbot.io integration alternatives
About Close CRM
Automate Close CRM tasks in Latenode to streamline sales processes. Automatically update deals, create tasks, or trigger follow-ups based on custom events. Integrate Close CRM with other apps like Slack or Google Sheets to centralize your data and communication flows using Latenode’s visual editor and flexible logic.
Similar apps
Related categories
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
See how Latenode works
FAQ Close CRM and Landbot.io
How can I connect my Close CRM account to Landbot.io using Latenode?
To connect your Close CRM account to Landbot.io on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Close CRM and click on "Connect".
- Authenticate your Close CRM and Landbot.io accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Close CRM leads from Landbot.io chatbot data?
Yes, you can! Latenode allows you to instantly create new leads in Close CRM from chatbot conversations, ensuring no potential customer is missed and saving your sales team valuable time.
What types of tasks can I perform by integrating Close CRM with Landbot.io?
Integrating Close CRM with Landbot.io allows you to perform various tasks, including:
- Create or update Close CRM leads based on Landbot.io interactions.
- Send personalized thank you messages via Landbot.io after a deal closes in Close CRM.
- Automatically log chatbot transcripts as notes on Close CRM lead records.
- Trigger Landbot.io flows when a Close CRM opportunity reaches a specific stage.
- Segment Landbot.io audiences based on Close CRM lead data for targeted messaging.
Can I use JavaScript to customize my Close CRM integration?
Yes! Latenode supports JavaScript code blocks, allowing you to create highly custom and complex Close CRM workflows beyond simple no-code options.
Are there any limitations to the Close CRM and Landbot.io integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require custom JavaScript code.
- Rate limits on the Close CRM and Landbot.io APIs may affect high-volume workflows.
- Real-time data synchronization depends on the responsiveness of both APIs.