Webhook step
Learn how to use the Webhook step in Tarvent Journeys, what it does, and when to use it in your automation flow.
What we'll cover
1 Concepts
What this step does
The Webhook step sends data to an external URL when a contact reaches the step, which is useful for triggering other systems or workflows.
Common settings you will see
- Name
- URL
- Method
- Headers
- Body
- View sample response
- Apply to which contacts
- Delete
- Save
Note: For inbound webhook setup (adding contacts into Tarvent), use the separate inbound webhook feature in audience settings.
2 How to configure this step
Here are the steps:
- Open the journey, and add or click the Webhook step.
- Enter the destination URL and configure the request settings.
- Configure any headers and the request body as needed.
- Use View sample response to review a sample response while testing.
- Set Apply to which contacts if needed, and click Save.
Warning: Test the webhook in a draft or controlled journey before using it in production, especially if it triggers external actions.
Use a step name that includes the target system, such as Webhook - CRM sync, so the journey map is easier to maintain.
3 Use cases and business examples
- System integration: Send contact or journey event data to an external app or internal service.
- Operations sync: Notify another system when a contact reaches a specific stage.
- Custom automation: Trigger a downstream process that is not handled directly inside Tarvent.
4 Step notes
Here is what to expect when this step runs in a live journey, including scheduling behavior, skip logic, and edge cases.
- Tarvent will make a single attempt at posted the JSON data to your webhook URL. If the server is down or the call is not successful, no further attempts will be made.
- The "EventType" property will always be null and the Initiator source will always be "Journey".
- The collection of profile records will vary depending on the number of custom data fields have been created for the associated audience.
{
"Id": "12345",
"DateUtc": "2025-02-20T14:30:00Z",
"AccountId": "67890",
"EventType": null,
"Initiator": {
"Source": "Journey"
}
"Payload": {
"audienceId": "1001",
"contact": {
"id": "5001",
"firstname": "John",
"lastname": "Doe",
"email": "john@example.com",
"rating": "3",
"status": "1",
"createdutc": "01/15/2025 10:30:00",
"sendformat": "0",
"language": "en",
"timezone": "America/New_York",
"optinutc": "01/15/2025 10:30:00",
"optoututc": "",
"modifiedutc": "02/18/2025 08:00:00",
"confirmedutc": "01/15/2025 10:35:00",
"longitude": "-73.935242",
"latitude": "40.730610",
"streetaddress": "123 Main St",
"streetaddress2": "",
"addresslocality": "New York",
"addressregion": "NY",
"postalcode": "10001",
"addresscountry": "US",
"journey_startedutc": "02/20/2025 14:00:00",
"lastdelivered": "02/19/2025 12:00:00",
"lastbounced": "",
"lastopened": "02/19/2025 13:00:00",
"lastclicked": "02/19/2025 13:05:00",
"lastreplied": "",
"lastshared": "",
"lastforward": "",
"last5delivered": "5",
"last5bounced": "0",
"last5opened": "4",
"last5clicked": "2",
"last5replied": "0",
"last5shared": "0",
"last5forward": "0",
"last5count": "5",
"groups": "["101","205"]",
"tags": "["vip","newsletter"]",
"profile": {
"300": "custom field value",
"415": "another custom value"
}
}
}
}
5 FAQ
What is the Webhook step used for?
It sends data out of Tarvent to another system when a contact reaches the step.
What does View sample response do?
It helps you review a sample response so you can validate the webhook setup while testing.
Can I limit which contacts trigger the webhook?
Yes. Use Apply to which contacts to limit which contacts run the step.
6 Need help?
If you need help setting up journeys, contact support. We’re happy to help.