Integrations · Build and automate
Send engagement events out and bring prospects in.
Subscribe an HTTPS endpoint to the RSVP, email, LinkedIn, and WhatsApp events your downstream systems need, with a delivery history for every attempt. In the other direction, each campaign can receive prospects from your forms, CRM, Clay, Zapier, n8n or Make, and they enter its omnichannel sequence automatically.
Requires an HTTPS endpoint that can receive POST requests.
What you get
Prospects in by webhook
Each campaign can receive prospects from a webhook, so a form, CRM, Clay, Zapier, n8n or Make sends a prospect straight into the campaign's sequence. No CSV upload and no manual start.
Independent endpoints
Register multiple endpoints, each with its own event subscriptions.
Selectable events
Subscribe each endpoint to the events it needs: RSVPs, email replies, clicks, bounces, unsubscribes, LinkedIn acceptances and replies, and WhatsApp replies.
Test payloads and headers
Send a schema-discovery test payload, with headers that include the event type and a unique event ID.
Durable delivery
Delivery attempts and a delivery history are recorded for every event.
At-least-once delivery
Delivery is at least once; deduplicate downstream using the event ID.
Full endpoint controls
Enable, disable, preview, test, edit, or delete an endpoint at any time. Social events fire only for channels connected on your plan.
How it works
- 1
Create a public HTTPS receiver
- 2
Register the URL
- 3
Select events
- 4
Send a test
- 5
Respond 2xx quickly
- 6
Deduplicate by event ID
- 7
To bring prospects in, send them to the campaign's webhook
Supported actions and data
Tantra can do
- POST RSVP, email engagement, LinkedIn, and WhatsApp events to your endpoint
- Receive prospects from your forms, CRM, Clay, Zapier, n8n or Make and add them to a campaign
- Retry delivery and keep a delivery history per attempt
Tantra receives
- A 2xx response from your endpoint acknowledging delivery
- Prospects added to a campaign from your forms, CRM or automation tool
Requirements and permissions
An HTTPS endpoint that can receive POST requests
A handler that responds quickly, within the documented timeout
Scope and limits
- Delivery is at least once; deduplicate downstream using the event ID.
- Endpoints must respond within the documented timeout.
- Calendar webhooks emit RSVP transitions, not unchanged snapshots.
- Social replies must belong to a sequence-linked conversation.
- n8n, Zapier, and Make connect through webhooks in both directions; they are not native Tantra connectors.
- Every prospect passes the same suppression, validation, sending-limit and sending-window checks, however it arrives.
Related integrations
Create a webhook.
Send engagement events to your HTTPS endpoint, and receive new prospects straight into a campaign.