Webhooks in Intempt#
Overview & Mental Model#
In Intempt, Webhooks are the outbound execution layer.They allow Intempt to send HTTP requests to external systems only after a meaningful business decision has been made inside a Journey.Unlike raw event tracking, Webhooks are:Journey-driven, not event-driven
Triggered only at decision points
Events explain what happened.
Journeys decide what matters.
Webhooks make something happen.
What Is a Webhook in Intempt?#
A Webhook is an outbound request sent by Intempt when a user reaches a specific Journey block.Internal backend notifications
Subscription lifecycle handling
Custom workflow automation
Why Webhooks Are Journey-Driven (Not Event-Driven)#
Webhooks are configured inside Journeys, not as global destinations.This ensures outbound calls:include final attribute values
represent meaningful business moments
triggering on every click
mirroring raw browser data
sending unstable or partial payloads
Webhook Configuration#
Where Webhooks Are Created#
Webhooks are created directly inside Journey blocks.❌ No reusable destinations
✅ One webhook = one business outcome
Request Type (HTTP Method)#
Each Webhook is configured with one HTTP method.Below are real, end-to-end examples of how each method is used in practice.
POST — Create / Notify#
Typical Use Cases#
Notify an internal backend
Live Example — CRM Lead Creation#
Journey Trigger
User completes signupURL: https://api.crm.example.com/leads
{
"eventTitle": "Signup Completed",
"timestamp": "2026-01-26T10:12:45Z",
"profile": {
"profileId": "usr_12ab45c99d77",
"email": "user@example.com",
"firstName": "Alex",
"plan": "free"
}
}
PUT — Update / Sync State#
Typical Use Cases#
Live Example — Subscription Upgrade Sync#
Journey Trigger
User upgrades planURL: https://billing.example.com/accounts/{accountId}
{
"eventTitle": "Plan Upgraded",
"timestamp": "2026-01-26T11:02:19Z",
"account": {
"accountId": "acc_a9213fbb892",
"previousPlan": "starter",
"currentPlan": "pro"
},
"profile": {
"profileId": "usr_12ab45c99d77",
"email": "user@example.com"
}
}
Confirms update with 200 OK
DELETE — Remove / Revoke#
Typical Use Cases#
Enforce consent revocation
Live Example — Consent Revocation#
Journey Trigger
User revokes marketing consentURL: https://email.example.com/subscribers/{email}
{
"eventTitle": "Consent Revoked",
"timestamp": "2026-01-26T11:45:10Z",
"profile": {
"email": "user@example.com"
},
"consent": {
"category": "marketing",
"action": "decline"
}
}
Removes email from mailing lists
Stops future communication
Responds with 204 No Content
Choosing the Right Method#
| Method | Use When You Want To |
|---|
| POST | Create or notify |
| PUT | Update existing state |
| DELETE | Remove or revoke |
Choose the method based on what the receiving system expects, not the Journey name.
Webhook Authentication#
Authentication is configured inside the Webhook block.Supported Methods#
Sent via Authorization header
Suitable for internal systems
Bearer tokens or API keys
Recommended for production
Webhook Payload Rules#
Generated at execution time
Identity is already resolved
Consent has already been validated
Failure Handling (Developer Responsibility)#
enqueue payloads for async processing
Common Mistakes to Avoid#
Triggering webhooks on every event
Using webhooks as event streams
Encoding business logic downstream
Treating webhooks as retry queues
Final Takeaway#
Webhooks are not tracking tools.the bridge between GrowthOS and your stack
Journeys decide intent.
Webhooks execute outcomes.Modified at 2026-01-29 15:28:02
