Guides
Connect Thoughtly to Zapier to trigger AI voice calls from any app in your stack and route call outcomes to your CRM, Slack, project tools, and more — no code required.
Last updated
If your lead conversion stack already runs through Zapier, Thoughtly slots in as both a trigger and an action — so voice, SMS, and email outreach become just another step in the Zap. This guide walks through authenticating the integration, building the two most common Zap patterns (triggering calls and routing call outcomes), and using Zapier's Filters and Paths to add conditional logic. No code required. If you have a Thoughtly account and a Zapier account, you can have your first Zap running in under fifteen minutes.
By the end, you will know how to fire an AI voiceAI voiceAn artificially generated, natural-sounding voice produced by a TTS model. Thoughtly supports a library of AI voices and brand-specific cloning. call from any of Zapier's 5,000+ apps, push Thoughtly call results into your CRMCRMThe system of record for leads, contacts, deals, and activity. Thoughtly reads from and writes to your CRM continuously. or project management tool, and pass per-call context so the agent greets each lead with the right information.
Thoughtly is published as a full app in the Zapier directory, not a webhook-only integration. That means you get structured triggers and actions with named fields — no raw JSON parsing needed on either side.
Open Zapier and click Create Zap. In the app search bar, type Thoughtly. Select the Thoughtly app. Zapier will prompt you to authenticate. Enter your Thoughtly API key (from Settings → Developer). Once authenticated, the connection persists across all future Zaps.
After authentication, Thoughtly appears in two places inside every Zap:
You can use both directions in the same multi-step Zap. For example: a new Google Sheets row triggers a Thoughtly call (action), and then a second Zap listens for the call completion (trigger) to route the outcome back to the sheet.
This is the speed-to-lead pattern. A new record appears in an upstream system — a form fill, a CRM contact, a spreadsheet row — and Zapier immediately fires a Thoughtly voice call to that lead.
Common trigger apps for inbound lead conversion:
| Trigger app | Trigger event | Typical use case |
|---|---|---|
| Google Sheets | New row added | Imported lead lists, manual uploads |
| HubSpot | New contact created | Inbound marketing leads |
| Typeform | New form response | Quote requests, enrollment applications |
| Google Forms | New form response | Service inquiries, appointment requests |
| Meta Lead Ads | New lead | Facebook/Instagram ad form fills |
| Salesforce | New lead or contact | Enterprise CRM-sourced leads |
| Gravity Forms | New form entry | WordPress lead capture |
Select the trigger app and event, then connect the account and test the trigger so Zapier has a sample record to work with.
Add a step and search for Thoughtly. Choose the Call a Lead action (or the equivalent action name in the Zapier catalog). Map the phone number field from the trigger into Thoughtly's phone field. Use E.164 format — for example, +18005551234. If your source data is not in E.164, add a Zapier Format step before the Thoughtly action to prepend the country code.
Metadata is the per-call context that travels with the call and is available inside the agent as variables. When you configure the Thoughtly action step, you can pass a JSON object that the agent reads at runtime. This is the same metadata system used in Thoughtly's native automations.
For example, if the trigger is a Typeform submission for an insurance quote request, you might pass:
{
"intent": "auto_insurance_quote",
"source": "typeform",
"zip_code": "90210",
"coverage_type": "full"
}Inside the agent prompt, reference these values with {{metadata.intent}}, {{metadata.zip_code}}, and so on. This lets the agent open the call with context: "Hi, I see you requested a full-coverage auto insurance quote for the 90210 area — let me walk you through your options."
Test the Zap in draft mode. Zapier sends a real test request to Thoughtly, and you should receive a test call on the mapped phone number within seconds.
The second core pattern uses Thoughtly as the trigger. After a call completes, Zapier receives the full call payload — transcriptTranscriptThe text record of a voice conversation, used for review, training, compliance audit, and search., summary, outcome, captured variables, duration — and routes it to the next system.
Create a new Zap. Choose Thoughtly as the trigger app and select the Call Completed event. Authenticate (your existing connection works), then test the trigger. Zapier pulls a recent call record so you can see the available fields.
Available fields from the Call Completed trigger include:
| Downstream app | Action | When to use |
|---|---|---|
| HubSpot | Update contact / Create deal | Write call outcome and captured fields back to CRM |
| Salesforce | Update lead / Create task | Log call summary, assign follow-up task to rep |
| Slack | Send channel message | Notify the sales team when a lead books or qualifies |
| Google Sheets | Create row | Append call log for reporting or QA review |
| ClickUp | Create task | Queue a follow-up task when the lead needs a callback |
| Notion | Create database item | Log deal notes for pipeline tracking |
| Google Calendar | Create event | Book the appointment the agent confirmed on the call |
Map Thoughtly's output fields into the downstream app's input fields. For CRM updates, map the contact phone number as the lookup key and write the outcome, summary, and captured variables as properties.
Not every call outcome should trigger the same downstream action. Zapier's Paths feature lets you branch based on Thoughtly's output, and Filters let you suppress actions entirely when conditions are not met.
Add a Paths step after the Thoughtly Call Completed trigger. Define a path for each outcome that matters:
This keeps downstream systems clean. Your CRM gets the right status, your reps get notified only when it matters, and no-action outcomes do not clutter the pipeline.
Use a Filter step when you want a simple gate. For example: only fire the downstream action if the captured variableVariableA named value the voice agent stores during a conversation — caller name, intent, qualifying answers — and uses to drive routing and post-call actions. "lead_score" is greater than 70, or only notify Slack if the call lasted longer than 60 seconds. Filters are lighter than Paths when you have a single condition.
Thoughtly ships native integrations for HubSpot, Salesforce, GoHighLevel, Calendly, Cal.com, Slack, Gmail, and others. These are tighter, faster, and support deeper functionality — bidirectional CRM sync, mid-call actions, real-time calendar availability lookups.
Use Zapier when:
For CRM-specific integrations like HubSpot and Salesforce, start with the native path. Guides for those are available: How to Sync AI Conversations Back to HubSpot and How to Sync AI Conversations Back to Salesforce.
+18005551234). If your trigger app outputs "(800) 555-1234" or "800-555-1234," the call will fail. Add a Zapier Format step to strip non-numeric characters and prepend the country code.Track these metrics to know if your Zapier-Thoughtly integration is performing:
| Metric | What it measures | Where to check |
|---|---|---|
| Speed-to-lead | Time from form fill to first Thoughtly call | Zapier task history + Thoughtly call logs |
| Call connection rate | Percentage of triggered calls that connect to a live person | Thoughtly analytics dashboard |
| Outcome distribution | Breakdown of booked / qualified / voicemail / not interested | Thoughtly analytics or CRM reports |
| Downstream completion rate | CRM records updated, tasks created, notifications sent | Zapier task history + downstream app |
| Zap error rate | Percentage of Zap runs that fail | Zapier task history |
If you are using Thoughtly's analytics dashboard, you can filter by phone number or metadata values to see how Zapier-sourced calls perform relative to other channels. For a deeper look at measurement, see How to Measure Conversion Lift from AI Follow-Up.
Yes. Search "Thoughtly" in the Zapier app catalog. The app is publicly available, supported, and includes both trigger and action modules.
Instant triggers (webhook-based) fire within seconds. Polling triggers check on a schedule — every 1 minute on Zapier's highest-tier plans, up to every 15 minutes on the free plan. For speed-to-lead workflows, use apps and events that support instant triggers or consider Thoughtly's native Incoming Webhook trigger for the tightest latency.
No. Calls triggered through Zapier are billed at standard Thoughtly per-minute rates. There is no surcharge for using Zapier as the trigger mechanism. Zapier charges separately based on your Zapier plan's task limits.
Yes. Use Zapier's Filter or Paths steps to control when the Thoughtly action fires. Common filters: only call if lead score is above a threshold, only call during business hours, only call if a phone number is present, or only call leads from a specific geography or campaign.
Use native integrations (HubSpot, Salesforce, GoHighLevel, Calendly, etc.) when they exist — they are faster and support deeper functionality like mid-call CRM lookups and real-time calendar availability. Use Zapier when the app you need does not have a native Thoughtly integration, when you want to fan out one event to multiple systems, or when your team's existing workflowWorkflowAn automated, multi-step process — usually triggered by an event (form fill, new lead) and orchestrating one or more voice / SMS / email actions. stack is Zapier-based. See the full integrations directory for what is available natively.