Skip to main content
Tantra

How Tantra works

From your first mailbox to booked meetings, in six steps.

Connect the accounts your team already owns, run email, LinkedIn, WhatsApp and calendar invitations from one platform, and see which campaigns produce replies, RSVPs and webinar attendance.

Start free trialExplore integrations
Illustrative workflow

Accounts

  • Google Workspace
  • Social accounts
  • Optional AI provider

Choose a campaign path

Calendar campaign

Invitations and RSVP

Sequence

Gmail, social steps, or both

Outcomes

  • Replies and reactions
  • RSVPs and attendance
  • Webhooks, API, or MCP

Your sending accounts

Your own AI provider

Channel-specific limits

No open tracking pixel

01 · Connect

  • Google Workspace admin
  • Marketer or SDR

Connect the accounts you send from.

Your Workspace admin authorizes Tantra once for Gmail and calendar invitations. Each sender links their own LinkedIn or WhatsApp account. Add an AI or webinar provider only if a campaign uses one.

Google Workspace setup guide
Required for Gmail or Calendar

Google Workspace

Your admin creates a Google service account (the identity Tantra sends through), grants it access to your domain, and uploads its key file. You then verify each mailbox.

Workspace setup
Up to 5 on Pro, 15 on Scale

Social channels

Each sender links their own LinkedIn account, or their existing WhatsApp number by QR code. No Google Workspace needed.

Compare channels
Optional

AI provider

Optional AI personalization for email and Calendar content. Sign in with a ChatGPT or Claude account, or bring an OpenRouter, Cerebras, or Novita key.

Compare AI providers
Optional attribution

Webinar provider

Connect Zoom with a Server-to-Server OAuth app from your Zoom admin, or WebinarGeek with an API key. Refresh attendance when you need it.

Explore webinars

02 · Choose

  • Marketer or SDR

Choose a sequence or a calendar campaign.

Sequences send ordered Gmail, LinkedIn and WhatsApp steps for prospecting and follow-up. Calendar campaigns send Google Calendar invitations when the response you want is an RSVP.

Compare campaign types

Calendar campaign

Choose it when the response you need is an RSVP.

Best for
Events, demos, webinars, and meeting invitations
Delivery
Google Calendar invitation
Primary signal
RSVP Yes, No, or Maybe
Sender
Verified Workspace calendar mailbox
Structure
One event, sent to your contact list
Webinar
Optional registration on a Yes or Maybe RSVP, plus attribution
Learn about Calendar campaigns

Omnichannel sequence

Choose it for ordered prospecting and follow-up touches.

Best for
Prospecting and follow-up across ordered touches
Delivery
Gmail, LinkedIn and WhatsApp steps, alone or combined
Primary signal
Reply, acceptance, tracked click, bounce, or unsubscribe
Sender
A ready account for every channel used
Structure
Ordered steps with per-step delays
Webinar
Attribution only; registration comes from calendar RSVPs
Learn about multichannel sequences

Calendar invitations currently run as their own campaign type, alongside your sequences.

03 · Build

  • Marketer or SDR

Bring in your contacts and write the steps.

Import a CSV, or send prospects in by webhook, API or AI assistant. Organize contacts into lists, then write each step with merge tags, spintax or optional AI. Invalid and role addresses are held for review, not emailed.

Build a multichannel sequence
  1. 1

    Import or send in prospects

    Map CSV columns to contact fields and group contacts into lists, or let webhooks, the API or your AI assistant add prospects to a campaign automatically.

  2. 2

    Check email addresses

    Syntax, mail server and role-address checks, plus your suppression list, keep risky addresses out. Failures wait in Needs review.

  3. 3

    Write the campaign

    Create the invitation, or add sequence steps with a delay before each one.

  4. 4

    Personalize where useful

    Merge tags and spintax, or optional AI for email subject and body and calendar invitation text.

Illustrative workflow

One possible mixed sequence

Stored copy

  1. Day 0 · Email

    Gmail email

  2. Day 2 · LinkedIn

    LinkedIn profile visit

  3. Day 4 · LinkedIn

    LinkedIn connection request

  4. Day 7 · WhatsApp

    WhatsApp message

Social-only sequences need no Workspace

For example: profile visit → connection request → message after acceptance. Without a Gmail step, no Workspace mailbox is needed.

LinkedIn and WhatsApp messages use plain-text templates, merge tags and spintax. Optional AI applies to email and calendar invitation text only, and your stored copy is sent whenever personalization cannot run.

04 · Launch

  • Marketer or SDR

Launch with every account checked.

Before launch, Tantra checks your senders, contact list, plan and schedule. At each send it applies per-account limits and the sending window in the recipient's time zone.

Sending windows and limits

Illustrative workflow

Launch readiness

  • Audience

    Contact list selected and usable

  • Sender coverage

    A ready account for every channel used

  • Timing

    Start date, delays, and send windows reviewed

  • Limits

    Account-level caps and channel controls applied

  • Stops on reply

    The remaining steps stop once a reply is detected

Review and launch

The right sender for each channel

Gmail and calendar sends are spread across your verified Workspace mailboxes. LinkedIn and WhatsApp steps send from the account you select.

Timing and per-account limits

Mailbox daily and hourly caps are account-level settings, separate from each campaign’s schedule. LinkedIn and WhatsApp accounts carry their own limits.

Missing channel data skips a step

A missing email, LinkedIn profile or WhatsApp number skips that step while the sequence continues. A LinkedIn message after a connection request waits for acceptance.

05 · Respond

  • SDR or account executive

Every reply routed to the people who act on it.

Gmail, LinkedIn and WhatsApp replies from your campaigns arrive in one Tantra inbox, with the campaign attached. The remaining steps stop once a reply is detected.

Use the unified inbox
Conversation view
Sample data

  • Avery from Northstar

    Gmail · Could Tuesday work?

  • Sam at Pine Labs

    LinkedIn · Connection accepted

  • Jordan from Atlas

    WhatsApp · Please send the agenda

Campaign context

Reply received from Avery

“Thanks for reaching out. Could Tuesday afternoon work for a short conversation?”

Reply receivedRemaining steps stoppedHuman follow-up

Threaded Gmail replies

Read and respond with the campaign and sender context attached.

Social replies

LinkedIn and WhatsApp replies to your campaigns appear in the same inbox.

Email safety signals

Bounces, unsubscribes, and suppression are processed automatically. Engagement is never inferred from an open pixel.

06 · Measure & automate

  • RevOps or marketing lead

Report results by campaign type.

Sequences report replies, clicks and bounces. Calendar campaigns report RSVPs. Webinars report registrants and attributed attendees. Send results to the rest of your stack with webhooks, the API or MCP.

Understand your analytics

Sequence outcomes

Sent, derived delivered (sent minus bounced), replies, tracked clicks when enabled, bounces, and unsubscribes.

Calendar outcomes

Invitations sent and RSVP Yes, No or Maybe for each calendar campaign.

Webinar outcomes

Registrants, attendees, attributed attendees, and Zoom watch time where the provider returns it after a requested sync.

Link a synced webinar

Attach Zoom or WebinarGeek to the campaign.

Invite and attribute

When the campaign opts in, a Yes or Maybe registers the contact for the webinar.

Request attendee sync

Compare invitees with attributed attendance after refresh.

Zoom and WebinarGeek catalog, registrant, and attendance refreshes are user-triggered, not continuous background syncs. Sequence webinar links provide attribution only and do not register contacts.

Automate

Connect campaigns to the rest of your stack, in both directions.

Developer integrations

Webhooks

Send selected Tantra events to an HTTPS endpoint, and receive prospects into a campaign from your forms, CRM, Zapier, n8n or Make. Outbound delivery is at least once, so consumers deduplicate by event ID.

Explore

REST API

Add prospects to campaigns and automate Tantra with revocable, account-level keys. The full key is shown once, at creation.

Explore

MCP Server

Operate dozens of Tantra tools, and let Claude, Claude Code, ChatGPT and other MCP-compatible AI assistants add qualified prospects to campaigns.

Explore

Prospects in, without a CSV

New

Prospects that arrive by webhook, API or AI assistant enter step one of the campaign automatically. Every prospect passes the same suppression, validation, sending-limit and sending-window checks, however it arrives.

Explore Prospect Intake

n8n, Zapier, and Make connect through the generic webhooks in both directions and are not native connectors. API-key scopes are not currently enforced, and MCP does not expose every action in the app.

Operational clarity

Know what runs automatically and what you refresh.

Automatic or scheduled

  • Scheduling and pacing for every active campaign
  • Sending, once each account passes its checks
  • Reply, bounce and unsubscribe handling
  • Calendar RSVP updates
  • Webhook delivery to your endpoints, with retries

User-triggered or configured

  • Connecting accounts and completing provider security checks
  • Zoom and WebinarGeek data refreshes
  • Launching or resuming a campaign
  • Choosing an AI default or tracking domain

Questions

Before you build the first campaign

Explore capabilitiesCompare integrationsRead setup guides

Run your next campaign on the accounts you already own.

Connect the required accounts, choose the campaign type, and add channels or integrations where the workflow needs them.

Start free trialExplore integrations