How to create a HTTP request block in a journey
How do I create a HTTP request block in a journey?
This article explains how to set up a HTTP request block inside an automation workflow. Follow these steps to send data from your journey 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 journey, make sure you have:
- An existing journey 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 journey
- Log in to your Flownally workspace.
- Go to the Journeys tab.
- Click an existing journey to edit it, or create a new one to open the editor automatically.
- Click on Add step at the end of a path, or on the + icon between two blocks, to add a new block.
- Choose the HTTP request block.
- Select the Method from the dropdown: GET, POST, PUT, PATCH, or DELETE.
- Enter the destination URL. It must start with https://.
- 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 contact details or event details.
- Specify the Timeout (seconds), from 1 to 60 seconds.
What happens after creating a HTTP request block in a journey?
After creating a HTTP request block in a journey, the system will send data to your external application when a contact reaches this step. The block has two paths: Success, when your server accepts the request, and Failure, when the request fails or times out. Click Add step on each path to decide what happens next. Your third-party platforms will update automatically without any manual work from your team.
Troubleshooting
HTTP request fails to send
This happens because the HTTP request URL contains a typo or is missing the https:// prefix. You must check the destination URL address and save the journey 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.