Make + Tantra via webhooks
Route Tantra engagement events through a Make custom webhook.
Receive selected Tantra campaign events in a Make custom webhook and route them into the scenario you build.
Requires a custom webhook in Make.
What you get
All 11 event types
Receive all 11 Tantra event types: calendar, email, LinkedIn, WhatsApp, and Telegram, with social events dependent on the matching add-on.
Example workflows
Update a CRM record, post a team alert, append to a spreadsheet, or create an internal task from a Tantra event.
Payload and field mapping
Each event ships a documented payload example with field-mapping tips for your Make scenario.
Deduplication
Deduplicate deliveries using the X-Tantra-Event-Id header.
How it works
- Step 1
Create a custom webhook in Make
- Step 2
Register the URL in Tantra and select events
- Step 3
Send a test event and branch on X-Tantra-Event
- Step 4
Return a 2xx quickly to keep delivery healthy
Supported actions and data
Tantra can do
- POST calendar, email, LinkedIn, WhatsApp, and Telegram events to your Make webhook
- Retry delivery and record delivery history for each attempt
Tantra receives
- A 2xx acknowledgment from your Make webhook
- No data flows back into Tantra from Make itself
Requirements and permissions
A custom webhook in Make
A Tantra outbound webhook endpoint registered and subscribed to events
Good to know
- There is no native Make module or OAuth connection; this recipe works entirely through the outbound webhook.
- Tantra does not own an action, module, or trigger inside Make; you build the scenario yourself.
- What you can do downstream depends on your own Make plan and scenario limits.
- Social channel events only send once the matching add-on is active.
Frequently asked questions
Does Tantra have a native Make module?
- No. This recipe routes events through a Make custom webhook; there's no Tantra-owned module.
Which events can I route into Make?
- All 11 production event types: 3 calendar, 4 email, 2 LinkedIn, 1 WhatsApp, and 1 Telegram, with social events dependent on the matching add-on.
How do I avoid duplicate scenario runs for one event?
- Deduplicate using the X-Tantra-Event-Id header on each delivery.
Related integrations
Recipesn8n
Receive Tantra campaign events in n8n and route them into the workflow you build.
- POST calendar, email, LinkedIn, WhatsApp, and Telegram events to your n8n webhook URL
- Retry delivery and record delivery history for each attempt
RecipesZapier
Send Tantra activity to a Zapier Catch Hook and route it into thousands of Zapier actions.
- POST calendar, email, LinkedIn, WhatsApp, and Telegram events to your Zapier Catch Hook
- Retry delivery and record delivery history for each attempt
Outbound Webhooks
POST calendar, email, LinkedIn, WhatsApp, and Telegram events to your HTTPS endpoint.
- POST calendar, email, LinkedIn, WhatsApp, and Telegram events to your endpoint
- Retry delivery and keep a delivery history per attempt
Create Tantra webhook.
Route Tantra activity through a Make custom webhook and build scenarios around it.