How to connect Landbot.io and Awork
Create a New Scenario to Connect Landbot.io and Awork
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 Awork will be your first step. To do this, click "Choose an app," find Landbot.io or Awork, 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 Awork Node
Next, click the plus (+) icon on the Landbot.io node, select Awork from the list of available apps, and choose the action you need from the list of nodes within Awork.

Landbot.io
⚙
Awork
Authenticate Awork
Now, click the Awork node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Awork settings. Authentication allows you to use Awork through Latenode.
Configure the Landbot.io and Awork 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 Awork 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
⚙
Awork
Trigger on Webhook
⚙
Landbot.io
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Landbot.io, Awork, 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 Awork integration works as expected. Depending on your setup, data should flow between Landbot.io and Awork (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 Awork
Landbot.io + Awork + Slack: When a lead qualifies through a specific event in Landbot.io, a new task is created in Awork to follow up with the lead. Subsequently, a message is sent to a designated Slack channel to notify the sales team about the new qualified lead and the created task.
Awork + Landbot.io + Google Sheets: When a task is updated to a completed status in Awork, the corresponding lead's status in Landbot.io is updated to 'customer' and the event is logged in Google Sheets for tracking and reporting purposes.
Landbot.io and Awork 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 Awork
Manage Awork tasks in Latenode to automate project updates and reporting. Trigger flows on new tasks, sync deadlines across tools, or create custom reports. Use Latenode's logic functions and webhooks to connect Awork to any system, crafting automated workflows without complex coding, and scale project management tasks efficiently.
Related categories
See how Latenode works
FAQ Landbot.io and Awork
How can I connect my Landbot.io account to Awork using Latenode?
To connect your Landbot.io account to Awork 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 Awork accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Awork tasks from new Landbot.io leads?
Yes, you can! With Latenode, automate Awork task creation from Landbot.io leads. Use no-code blocks and JavaScript for advanced logic, ensuring seamless lead management and efficient task assignment.
What types of tasks can I perform by integrating Landbot.io with Awork?
Integrating Landbot.io with Awork allows you to perform various tasks, including:
- Create Awork tasks automatically from new Landbot.io chatbot submissions.
- Update Awork task statuses based on Landbot.io conversation outcomes.
- Add Landbot.io user data to Awork projects as new contacts.
- Send personalized follow-up messages via Landbot.io for Awork task updates.
- Trigger Awork project updates based on Landbot.io chatbot responses.
Can I use custom variables from Landbot.io within Awork tasks?
Yes, Latenode lets you map Landbot.io variables to Awork task fields. Utilize no-code blocks or custom JavaScript to dynamically populate task details.
Are there any limitations to the Landbot.io and Awork integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex Landbot.io chatbot flows might require advanced configuration.
- Awork API rate limits may affect high-volume task creation workflows.
- Custom field mappings require careful setup for data consistency.