n8n Integration With Trigger Automation Block

Pau Sanchez Updated by Pau Sanchez

Want to automate what happens after a user interacts with your Landbot? With the n8n Integration using the Trigger Automation block, you can seamlessly send user inputs to an n8n workflow to kick off any automation you design.

This setup is a one-way connection: Landbot pushes the data to n8n, but it won’t display or use any response from n8n in the chat. It’s ideal for logging information, triggering processes, or sending data to other apps while keeping the conversation in Landbot flowing smoothly.

In this guide, we’ll show you how to configure the Trigger Automation block in Landbot, set up the webhook in n8n, and test the integration step by step.

Prepare Landbot
  1. Firstly, we have to make a little flow for collect information, like name, email, age, etc.

The information that we collect, will be stored in variables, that we will send to n8n. As in the example below, we are storing the name input in the variable @name, that we will use later

  1. Then let's set add a Trigger automation block.

Create n8n workflow
  1. After set a Trigger automation block, let's open n8n and create a new workflow

  1. Then click on "Add first step" to select how we will trigger the workflow, and search for "Webhook"

  1. Once added, we will set the request from GET to POST, and make sure the webhook is listening

  1. Then below copy the Test URL, later once is set up you will need to use the Production URL:

Prepare Landbot request to n8n
  1. Now paste the Test URL in the Trigger Automation block:

  1. Now we are going to set the variables we want to send to n8n, scroll down and go to Set fields (variables) to be sent section, where you can see we are setting values to the Landbot variables:
  2. And click on Test webhook trigger button:
  1. If you scroll down, you will see the response from n8n:

  1. As long as the status code is 200, means our request is successfully sent.

Inside of n8n check request data
  1. Let's turn back to n8n:

We can see that the trigger request has been successful and the data has arrived correctly and can be used in your workflow

Now that the Trigger Automation set up is working, make sure to update later the URL for the Production URL

Was this article helpful?

Contact