Skip to main content

How to create a HTTP request block in a chatbot

LLM
View as Markdown
Open llms.txt

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 on your journey.
  • 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 destination URL to receive your automated payload data.

How to create a HTTP request block in a chatbot

  1. Log in to your Flownally workspace.
  2. Go to the Chatbots tab.

  1. Click an existing chatbot to edit it, orcreate a new one to open the editor automatically.

  1. Click on + icon to add a new block.
  2. Choose the HTTP Request block.

  1. Select the HTTP Method from the dropdown.
  2. Enter the destination URL.
  3. Optionally click + Add header to supply specific header Names and Values.
  4. In the Body dropdown, select JSON if you need to send data, or None if no payload is required.
  5. If you selected JSON, enter your data payload into the JSON body text field.
  6. Specify the Timeout duration (in seconds).

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.

Troubleshooting

HTTP request fails to send

This happens because the HTTP request URL contains a typo or is missing the required 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.

Related articles