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

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

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

Discourse
⚙
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 Discourse 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 Discourse 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
⚙
Discourse
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Discourse, 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 Discourse and Landbot.io integration works as expected. Depending on your setup, data should flow between Discourse 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 Discourse and Landbot.io
Discourse + Landbot.io + Slack: When a new topic is created in Discourse, use Landbot.io to send a text message to the user asking for more details about the issue. Then, send a message to a Slack channel notifying the support team about the new issue and include the details gathered by Landbot.io.
Landbot.io + Discourse + Airtable: When user feedback is received via Landbot.io, a new topic is created in Discourse to discuss the feedback. Also, the feedback data is stored in Airtable for analysis and tracking purposes.
Discourse and Landbot.io integration alternatives
About Discourse
Integrate Discourse with Latenode to automate community management. Trigger actions based on new topics or replies. Automatically analyze sentiment, flag urgent issues, and update your CRM. Build custom moderation flows with Latenode's no-code tools, AI nodes, and flexible JavaScript functions, scaling support without manual effort.
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 Discourse and Landbot.io
How can I connect my Discourse account to Landbot.io using Latenode?
To connect your Discourse account to Landbot.io on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Discourse and click on "Connect".
- Authenticate your Discourse and Landbot.io accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically update Discourse topics from Landbot.io surveys?
Yes, you can! Latenode's visual editor makes it easy to trigger updates based on survey responses. Keep your community informed and engaged with zero code.
What types of tasks can I perform by integrating Discourse with Landbot.io?
Integrating Discourse with Landbot.io allows you to perform various tasks, including:
- Create new Discourse topics from Landbot.io chatbot interactions.
- Send personalized welcome messages in Discourse upon Landbot.io signup.
- Update user roles in Discourse based on Landbot.io qualification surveys.
- Post summaries of Landbot.io conversations to Discourse for team review.
- Trigger Landbot.io chatbot flows based on specific Discourse forum activity.
How do I handle errors in my Discourse workflows?
Latenode offers robust error handling. Use "Try/Catch" blocks to gracefully manage failed requests and ensure workflow stability.
Are there any limitations to the Discourse and Landbot.io integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Discourse and Landbot.io APIs may affect performance.
- Complex data transformations might require JavaScript knowledge.
- Real-time synchronization depends on the polling interval configured.