The Webhook Node allows you send Profile Data to another system.
In this Article
About the Webhook Node
The Webhook node allows you to make calls to an external API and make use of the data that you're currently tracking with your other existing integrations and products.
Send any data from a profile's attributes and if the MA flow is triggered by an event any data in that event can be sent.
Data stored in older events can not be sent with the webhook. Meaning only data from the event triggering the flow is the event data you can send. Events already stored on a profile can not be send.
It is not possible to add data to a Profile using the webhook.
Setting Up the Node
1. Drag the Webhook Node into the canvas and click it to open it up and see all available options.
2. Choose a http method on the http dropdown.
While the action of the HTTP method depends on the API you're using, here's a rundown of what each method generally does in most cases.
GET: Retrieve data from the path/endpoint.
POST: Create new data into the path/endpoint.
PUT: Update existing data in the path/endpoint.
DELETE: Delete data in the path/endpoint.
PATCH: Partially update data in the path/endpoint.
Please note, currently, the webhook Node will send your request as a GET parameter instead of a request body payload.
3. Enter the URL. This is the URL to the endpoint where the Webhook will call. The Webhook node supports static parameters.
Add Profile Data
4. Next, define the data you want to send.
Add Profile Data as URL Parameter
You can add Profile Data through URL Parameters. Choose which parameters to send and choose the data from the drop down menu.
5. Choose the Attribute (Default or Custom) or Event data you wish to send to your API.
If your Listen Node is not listening for an Event, the Event Data option will not be available in the Webhook node.
Add Header Data
6. If you want to add headers set it up here by specifying the name and value for each header you want to send. Repeat to add yet another header.
7. From the Response drop-down menu, choose between a string value or a status code for the response type.
8. In Expected response, add an expected response as a string value or status code.
9. In Error Handling, define the behaviour of the Webhook Node whenever the API response doesn't match your criteria or there is an expected error (for example, the URL is incorrect or the server doesn't respond.
Next node yes: Profiles continue to the next node via the Yes path way.
Next node no: Profiles continue to the next node via the No path way.
Exit flow: Profiles exit the flow.