Webhooks#
1. Overview#
Through Webhooks, you can send HTTP requests to a third-party application whenever an event or action occurs on your application.When an event happens on your webpage, you can notify a third-party application automatically without continuously polling for data.Whenever an event occurs in Intempt, a request will be sent in JSON format to the Webhook URL you’ve configured.The URL will be called automatically every time a specified action or event happens for users in Intempt. For example, whenever a new contact is added, you can configure Intempt to push data to your application’s webhook URL automatically via a Journey action that uses a Webhook destination.
2. Webhook Configuration#
Creating a Webhook Destination#
Unlike other destinations, the Webhook destination is created directly inside the Journey block.Request Type#
You can configure one of the following HTTP methods:POST — Sends data to a specific URL and expects the resource to handle the request.
PUT — Places or replaces a resource at a specific URL. Creates it if it does not exist.
DELETE — Requests that the server delete the resource identified by the URL.
Examples of Request Types#
POST — Create a new lead in a CRM system when a new user signs up. Intempt sends a POST request with user details in JSON.
PUT — Update an existing resource when a user changes their subscription tier. Intempt sends a PUT request with updated plan information.
DELETE — Remove a user from a mailing list when they unsubscribe. Intempt sends a DELETE request to the mailing system’s URL.
URL#
Define the Webhook destination URL that Intempt should call.
3. Webhook Authentication#
If your third-party application URL is protected, you can authenticate using:Basic Authentication#
Pass a Username and Password for accessing the URL.Token Authentication#
Pass a token or API key to authenticate and access the URL.
4. Payload Structure#
Webhook requests include default event trigger information in the JSON body.Custom Payload#
Add your own contact or event properties.
These will be included as JSON in the request body.If additional metadata is required (e.g., security information), you can enable and define custom HTTP headers.Note: Example payloads were not included in the provided content.
When available, they can be added to this section.
5. Journey → Webhook Block (Developer Notes)#
The Webhook block exists directly inside the Journey builder.
It is not created in the global Destinations list.When a user reaches this block in a Journey:Intempt triggers the HTTP request
The configured payload is sent to the destination URL
No polling or manual syncing is required
6. Integrations & Use Cases#
Webhooks allow Intempt Journeys to connect with external tools seamlessly.Examples#
Google Sheets — Append a row via POST when a new order is placed.
CRM systems (HubSpot, Salesforce, Pipedrive) — Create or update contact records when user profiles change.
Email marketing tools (Mailchimp, SendGrid) — Add or update subscribers based on user actions.
Internal APIs — Push structured event data to your backend for analytics or custom workflow automation.
Modified at 2025-12-03 12:46:38
