The dynamic variables (POST) in the Outgoing Webhook is in closed beta. If you’re interested in using it, please reach out to your success manager.
The Outgoing Webhook node is a fundamental building block of Journeys, designed to enhance your flow by seamlessly connecting with external APIs.
It enables you to perform GET and POST requests, import specific dynamic variables from API responses, send data from your system to charles, and then utilize them in your flow.
Here we’ll guide you through the setup and usage of the Outgoing webhook node.
Configuring the node
GET request
Screenshot of the Flow we've built in the video
Screenshot of the Flow we've built in the video
Configure the node by specifying the GET request method
Add the URL you want to retrieve data from, as well as an authorization header (if necessary)
Preview the available data and select which variables you wish to further use within the flow
Example
Below you can see that we’ve used a GET request to retrieve the dynamic coupon code and then use that data within a message node. Effectively sending the dedicated coupon code to a customer via WhatsApp.
Once variables are imported, they can be easily integrated into the body of messages or used in the condition node.
POST request
POST Request
Screenshot of the Flow we've built in the video
Screenshot of the Flow we've built in the video
Configure the node by specifying the POST request method
Add the URL you want to send data to, as well as an authorization header (if necessary)
Build the payload with the data you want to send. Please use a valid JSON format
For some users, the data can be retrieved from the “Insert variable” button in order to access dynamic variables such as contact and custom properties
Preview the values from the payload, give the variables group a name so that they can be further sent
Variable formats
Here’s how to format the variables in the payload body.
Contacts
Variable | Description | Format |
Preferred name | Contact’s preferred name in WhatsApp | {{flowbuilder_trigger_person.preferred_name}} |
First name | Contact’s first name in WhatsApp | {{flowbuilder_trigger_person.first)name}} |
Last name | Contact’s last name in WhatsApp | {{flowbuilder_trigger_person.last_name}} |
Nickname | Contact’s WhatsApp nickname | {{flowbuilder_trigger_person.nickname}} |
Contact’s email | {{flowbuilder_trigger_person.email}} |
Custom properties
{{flowbuilder_custom_properties.[technical_name]}}
You can find the technical name of the 🎨Custom properties in Settings.
Orders
Variable | Description | Format |
Order name | Name of the order | {{flowbuilder_trigger_order.name}} |
Order summary | Summary of the order | {{flowbuilder_trigger_order.summary}} |
Total amount | Total order amount (gross) | {{flowbuilder_trigger_order.amount_total_gross}} |
Example
Below you can see that we’ve sent data (including the coupon code as the data variable) to Zapier.
Once the variables are set, the flow can be further built and when triggered, it will send the particular set of data to the connected API. Once variables are imported, they can be easily integrated into the body of messages or used in the condition node.
Using variables in nodes
Message & Update nodes
Use the variable data in message and update nodes by selecting ‘Add variable’:
Condition node
Use the variable data in the condition node by selecting the ‘Flow variable’ event:
