Receive outbound webhooks
Register an endpoint, select channel actions, inspect payloads, and understand delivery retries.
Open in Tantra
These open the app in a new tab. You may be asked to sign in.
Overview
A webhook sends campaign activity from Tantra to an HTTPS URL you control. Each endpoint has its own action subscriptions, so one endpoint can receive calendar RSVPs while another receives email or messaging replies.
Register an endpoint
- Open Webhooks and click Create webhook.
- Enter a title and a public HTTPS URL.
- Select one or more actions under Calendar, Email, LinkedIn, WhatsApp, or Telegram.
- Click Send test payload to verify the entered URL with an automation-setup schema containing fields and conditions for every supported action.
- Click Create webhook.
LinkedIn, WhatsApp, and Telegram are always shown. Their checkboxes are disabled when that channel’s add-on is inactive, with a link to Billing → Add-ons.
The webhook table shows status, successful delivery count, last delivery time, and selected actions. Its row buttons preview JSON, send a test, edit, or delete the endpoint.
Triggering conditions
- Calendar reconciliation runs about every 10 minutes, but it sends only when an individual guest changes to Yes, No, or Maybe. It does not send unchanged snapshots or “Needs action.”
- Email events are emitted when bounce, tracked click, real reply, or unsubscribe processing succeeds.
- LinkedIn, WhatsApp, and Telegram replies come from verified inbound messaging callbacks and apply only to conversations linked to a sequence.
- LinkedIn connection acceptance comes from a real-time relationship callback, with periodic reconciliation as a missed-callback safety net.
See Webhook event triggers for every event name and field.
Test and headers
Click Send test payload in the create or edit dialog to verify the currently entered URL before saving. The send icon on an existing webhook performs the same check for its saved URL. Both post a webhook.test schema-discovery payload with every supported condition and possible production field path, plus the endpoint's selected subscriptions. Test requests include X-Webhook-Test: true. Real and test deliveries also include X-Tantra-Event, X-Tantra-Event-Id, and User-Agent: Tantra-Webhook/1.0.
The test payload is deliberately a superset for configuring automation tools. Real deliveries still contain exactly one eventType and only the fields relevant to that event.
Delivery and retries
- Endpoints must return a
2xxresponse within 15 seconds. - Email and social events are queued and retried on an immediate, 1-minute, 5-minute, and 30-minute schedule before dead-lettering.
- Calendar RSVP deliveries make up to three attempts with short exponential delays.
- One failing endpoint does not block another endpoint.
- Delivery is at-least-once; consumers should deduplicate by
X-Tantra-Event-Id.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Test delivery fails | URL is unreachable or did not return 2xx | Verify public HTTPS access and response status |
| No calendar delivery | No guest changed to Yes, No, or Maybe | Wait for a real RSVP transition and the next reconciliation |
| Messaging actions are disabled | Channel add-on is inactive | Activate it under Billing → Add-ons |
| No social reply delivery | Conversation is unrelated to a sequence, add-on is inactive, or callback routing is unhealthy | Verify enrollment linkage, entitlement, account health, and provider callback registration |
| Deliveries repeat | Retry after an uncertain response | Deduplicate on X-Tantra-Event-Id |
FAQ
Can one endpoint subscribe to only email replies?
Yes. Edit it, clear every other action, and leave Email replied selected.
Can I pause delivery without deleting the endpoint?
Yes. Turn off the endpoint’s status toggle.
Does this include email link clicks?
Yes, when click tracking is enabled for the campaign and Email clicked is selected. Bot clicks are filtered before the event is emitted.
How does Tantra know about messaging replies?
The messaging provider posts signed account, message, and relationship events to Tantra’s server callback. Tantra verifies the signature, mirrors the message, associates it with a sequence enrollment, and then emits the selected customer webhook event. A reconciliation job covers missed callbacks.
Related articles
Was this article helpful?