Skip to main content
Tantra

How Tantra works

From connected accounts to measurable conversations.

Connect the accounts your team already owns, choose Calendar outreach or a channel-flexible sequence, then let Tantra schedule delivery and bring replies, RSVPs, and attributed webinar outcomes back into view.

Start freeExplore integrations
Illustrative workflow

Accounts

  • Google Workspace
  • Social accounts
  • Optional AI provider

Choose a campaign path

Calendar campaign

Invitations and RSVP

Sequence

Gmail and/or social steps

Outcomes

  • Replies and reactions
  • RSVPs and attendance
  • Webhooks, API, or MCP
  • Your sending accounts
  • Your AI-provider key
  • Channel-specific limits
  • No open tracking pixel

01 · Connect

Connect only what your workflow needs.

Google Workspace supplies Gmail and Calendar sender identities when those actions are used. Add social, AI, and webinar providers only when the campaign needs them.

Required for Gmail or Calendar

Google Workspace

Authorize a service account once, upload its JSON, then verify the Workspace mailboxes you want to use.

Workspace setup
Paid add-on · $10/month

Social channels

Link a ready account for each enabled LinkedIn, WhatsApp, or Telegram action in the sequence.

Compare channels
Bring your own key

AI provider

Connect OpenRouter, Cerebras, or Novita when eligible email or Calendar content needs AI personalization.

Compare AI providers
Optional attribution

Webinar provider

Connect Zoom or WebinarGeek, then trigger catalog and attendance syncs when the campaign needs them.

Explore webinars

02 · Choose

Two campaign types, chosen by the outcome you want.

Calendar campaigns and outreach sequences are separate workflows. Choose one when you create the campaign; compare their outcomes later through reporting and automation.

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
Event plus distribution plan
Webinar
Optional positive-RSVP registration and attribution
Learn about Calendar campaigns

Channel-flexible sequence

Choose it for ordered prospecting and follow-up touches.

Best for
Prospecting and follow-up across ordered touches
Delivery
Any valid mix of Gmail, LinkedIn, WhatsApp, and Telegram
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; no Calendar RSVP trigger
Learn about multichannel sequences

The important boundary: Calendar is not a channel inside the sequence builder. A sequence can mix Gmail and enabled social actions, or contain only social actions, while a Calendar campaign remains separate.

03 · Build

Build from a clean audience and a clear next action.

Import and organize contacts, then compose either the invitation or the ordered sequence. Personalize only where it improves the message and the required data is available.

  1. 1

    Import and organize

    Map CSV fields, group contacts into lists, and keep campaign membership visible.

  2. 2

    Validate email enrollment

    Syntax, MX, role-address, suppression, and quarantine checks keep clearly unsafe email recipients out.

  3. 3

    Compose the campaign

    Create the event or add sequence steps, delays, channel actions, and stored templates.

  4. 4

    Personalize where useful

    Use merge tags and spintax, or optional AI for eligible email subject/body and Calendar descriptions.

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 are supported

For example: profile visit → connection request → accepted-connection message. No Gmail step means no Workspace sender is required for that sequence.

Social messages use plain-text templates, variables, and spintax. Optional campaign AI applies only to eligible email and Calendar content, and stored copy remains the fallback when personalization cannot run.

04 · Launch

Launch only after every sender and channel is ready.

Tantra checks configuration, connected accounts, audience, entitlements, and timing before work begins. Each engine checks channel readiness and limits again when work executes.

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

  • Stop behavior

    Reply reactions protect against unwanted follow-up

Review and launch

Sender pools and selected accounts

Workspace senders distribute Gmail or Calendar work. Social steps use the selected connected account for that channel.

Timing and per-account limits

Email schedules and account-level daily/hourly caps remain separate from social action limits. There is no single universal quota.

Coverage can vary by contact

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

Tantra controls its own scheduling, retries, and limits. It cannot guarantee inbox placement or prevent a third-party network from restricting an account.

05 · Respond

Bring replies back to the people who can act.

Threaded Gmail replies and mirrored supported social conversations appear in Tantra's inbox surfaces. A sequence-linked response updates enrollment so the next inappropriate follow-up can stop.

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 receivedEnrollment updatedHuman follow-up

Threaded Gmail replies

Read and respond with the campaign and sender context attached.

Supported social replies

Mirror sequence-linked LinkedIn, WhatsApp, and Telegram responses where supported.

Email safety signals

Handle bounces, unsubscribes, and suppression without pretending an open pixel is engagement.

06 · Measure & automate

Measure the outcome each channel can actually provide.

Sequence, Calendar, and webinar reporting use different signals. Keep those differences visible, then move the supported outcomes into the rest of your workflow.

Sequence outcomes

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

Calendar outcomes

Invitation progress and RSVP Yes, No, or Maybe, without treating Calendar as an email sequence step.

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

An opted-in Calendar Yes/Maybe can register the contact.

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 support attribution but do not create reply-driven registration.

Automate

Move supported outcomes into the rest of your stack.

Developer integrations

Outbound webhooks

Subscribe an HTTPS endpoint to any of 11 selectable event types. Delivery is at least once, so consumers deduplicate by event ID.

Explore

REST API

Use a revocable account-level key with optional expiry on supported API-key routes. The full key is shown once.

Explore

MCP Server

Operate dozens of supported Tantra tools through local stdio or hosted Streamable HTTP from a compatible client.

Explore

n8n, Zapier, and Make consume generic webhooks; they are not native connectors. API-key scopes are not currently enforced, and MCP does not expose every UI action.

Operational clarity

Know what runs automatically and what you refresh.

Automatic or scheduled

  • Active-campaign scheduling and engine-specific pacing
  • Send execution after readiness checks
  • Reply, bounce, unsubscribe, and supported callback processing
  • Calendar RSVP reconciliation
  • Durable webhook delivery attempts

User-triggered or configured

  • Initial connections and provider checkpoints
  • Zoom and WebinarGeek data refreshes
  • Launching or resuming a campaign
  • Enabling paid social add-ons
  • Choosing an AI default or tracking domain

Questions

Before you build the first campaign

Can one campaign send calendar invitations and social steps?

No. Calendar campaigns are separate. A sequence can use any valid mix of Gmail, LinkedIn, WhatsApp, and Telegram steps, including social-only.

Do I need every integration before I start?

No. Connect only the accounts needed by the campaign type and channels you choose. Google Workspace is required for a Calendar campaign or a sequence that contains Gmail; a social-only sequence does not require it.

Is AI required?

No. Templates, merge tags, and spintax work without a customer AI provider. A connected default provider enables supported email and Calendar personalization; social steps remain template-based.

Does Tantra automatically refresh webinar attendance?

No. Zoom and WebinarGeek data refresh when you trigger the relevant sync.

What stops a sequence after a reply?

A detected sequence-linked reply updates the enrollment so inappropriate scheduled follow-up can stop according to the live channel behavior.

Explore capabilitiesCompare integrationsRead setup guides

Build the outreach path your next campaign needs.

Start with the outcome, connect the required accounts, and add channels or integrations only where they improve the workflow.

Start freeExplore integrations