Zapier
Connect Kickcall AI & Automate Phone Calls
Written By Maruf Ansari
Last updated About 2 hours ago
The Zapier integration connects your Kickcall account with Zapier so you can bring AI-powered phone calls into your Zaps. Once connected, you can trigger outbound calls from any Zap, pass dynamic data into your Kickcall AI agent, and pull the call summary back to decide what happens next.
What you can build: lead follow-up, lead qualification, appointment reminders, patient follow-up, customer follow-up, sales outreach, and any other multi-step phone automation.
Step 1: Connect Kickcall to Zapier
Before you build a phone call Zap, connect your Kickcall account to Zapier. You need an active Kickcall account and a Kickcall API key.
Get your Kickcall API key
Log in to your Kickcall dashboard.
Go to API Keys in the left sidebar.
Create a new key, or copy an existing one.
Store the key securely - you will need it during the Zapier connection.
Important: Treat your API key like a password. Never share it publicly, commit it to a repository, or include it in screenshots or shared Zaps.
Connect Kickcall AI in Zapier
In the Zap editor, add a new step and search for Kickcall AI.
Select any Kickcall AI action to begin - for example, Create a Phone Call.
When prompted to choose an account, click Sign in.
Enter your Kickcall API key and the business email associated with your Kickcall account.
Click Yes, Continue to save the connection.
Once the connection succeeds, all Kickcall AI actions become available in any Zap in your Zapier account.
Step 2: Create a phone call Zap
Create a Zap that will trigger the outbound call. Common triggers include:
A new lead submits a form (Typeform, Google Forms, Webhooks by Zapier)
A row is added to Google Sheets or Airtable
A CRM such as HubSpot or Salesforce fires a new contact event
A Schedule by Zapier trigger fires for an appointment reminder
A simple Zap looks like this: Trigger → Kickcall AI (Create a Phone Call) → Filter (check call status) → Slack notification.
Tip: Any Zapier trigger that makes sense for your business will work. Kickcall is designed to sit inside your existing automation and accept data from any earlier step.
Step 3: Configure the Create a Phone Call action
In your Zap, click + to add an action step.
Search for Kickcall AI and select the Create a Phone Call event.
Fill in the required fields, mapping values from earlier steps where needed.
Required fields
Location - the Kickcall location the call should be created under.
Agent - the Kickcall AI agent that will handle the outbound call.
To Number - the phone number Kickcall should call. Map it dynamically from your trigger step, for example the phone field from a form submission.
Important: The mapped number must include a valid country code and follow E.164 international format, for example +12345678900. Calls may fail to initiate without it.
Optional fields
LLM Dynamic Variables - pass information from Zapier into the AI agent's prompt: the customer's name, appointment time, lead details, or any custom CRM field the agent should know before it speaks. Applies to the Response Engine only. Supply this field as raw JSON.
Metadata - arbitrary key/value pairs for your own reference, useful for identifying and tracking a call later when several Zaps or campaigns create calls. Also supplied as raw JSON. Not used by the agent.
Important: Both fields expect valid JSON. Check for missing quotes, trailing commas, or stray characters before turning the Zap on, and confirm any mapped values resolve to plain text rather than an object or array.
Copy your Location ID and Agent ID straight from the URL of the agent dashboard in Kickcall.
Step 4: Store the Interaction ID
When Create a Phone Call runs successfully, Kickcall returns details about the new call, including the Interaction ID - the unique identifier for that call.
Because Zaps run linearly, you have two options:
Immediate processing - pass the Interaction ID straight into the next step in the same Zap.
Storage for later - write it to Google Sheets, Airtable, or your CRM alongside the contact record so a separate Zap can look it up afterward.
Important: Make sure the Interaction ID is stored successfully before you use it with the Get a Call action.
Step 5: Retrieve call details
Use the Get a Call action to pull the results of a call you created earlier:
Add a new step to your Zap, or create a follow-up Zap.
Search for Kickcall AI and select the Get a Call event.
Select the same Location and Agent used to create the call.
Provide the Interaction ID, mapped from wherever you stored it in Step 4.
Test the step to pull the finalized call data.
Step 6: Build your Zap automation
Everything returned by Get a Call can feed Zapier's Filter and Paths steps. Route the summary into your CRM, post a Slack message recapping the call, or branch on the hangup reason to send a follow-up email or schedule a retry.
A full example looks like this: Trigger → Create a Phone Call → Store Interaction ID → Get a Call → Paths (branch on call outcome) → follow-up action.
Troubleshooting
Call failed to initiate - usually an incorrect or unsupported phone number format. Confirm the number includes a valid + country code, for example +12345678900.
Authentication failed / 401 Unauthorized - the API key is invalid or expired. Generate a new key in your Kickcall dashboard and reconnect the account in Zapier.
Dynamic Variables or Metadata error - invalid JSON. Check for missing quotes, trailing commas, or stray characters, and make sure any mapped values resolve to valid strings.
Get a Call does not return the expected information - the Interaction ID is missing or incorrect. Confirm the ID returned by Create a Phone Call was stored before Get a Call runs.
Zap runs but no call is placed - check the Zap history for a skipped or errored step, and confirm the Zap is published and turned on, not left in draft.
If you still need help, submit a ticket to the Kickcall support team and include your Kickcall account email, the Zap name, the Kickcall action being used, the Interaction ID if one was generated, and the exact error message from the Zap history. That detail lets the team resolve the issue much faster.