How to create a HTTP request block in a chatbot
How do I create a HTTP request block in a chatbot?
This article explains how to set up a HTTP request block inside a chatbot. Follow these steps to send data from your chatbot to external applications automatically. This ensures your third-party systems update instantly when a customer reaches this step.
In this article, you will learn how to
- Configure a HTTP request block in your chatbot.
- Set up the destination URL and payload correctly.
- Resolve data transfer issues with external servers.
Before you start
Before creating a HTTP request block in a chatbot, make sure you have:
- An existing chatbot to add a HTTP request block.
- A valid HTTPS destination URL to receive your automated payload data.
How to create a HTTP request block in a chatbot
- Log in to your Flownally workspace.
- Go to the Chatbots tab.
- Click an existing chatbot to edit it, or create a new one to open the editor automatically.
- Click on Add step after a block, or on the + icon on a connecting line, to add a new block.
- Choose the HTTP request block.
- Select the Method from the dropdown.
- Enter the destination URL.
- Optionally, open Headers and click Add header to supply specific header names and values.
- In the Body dropdown, select JSON if you need to send data, or None if no payload is required.
- If you selected JSON, enter your data payload into the JSON body field. Type {{ to insert variables, such as the contact's name.
- Specify the Timeout (seconds).
- Add the next steps for both paths on the canvas: Success and Failure.
What happens after creating a HTTP request block in a chatbot?
After creating a HTTP request block in a chatbot, the system transmits data payloads to your third-party application. The external tool receives user information automatically when a customer hits this step. The chatbot then follows the Success path, or the Failure path if the request doesn't succeed.
Troubleshooting
HTTP request fails to send
This happens because the HTTP request URL contains a typo or is missing the required https:// prefix. You must check the destination URL address and save the block again to fix it.
External server rejects data
This occurs because the payload format contains syntax errors or missing data fields. You need to verify the JSON payload format in your block settings to match your server rules.