Make
Connect Kickcall AI & Automate Phone Calls
Written By Maruf Ansari
Last updated About 1 hour ago
The Make.com integration connects your Kickcall account with Make so you can bring AI-powered phone calls into your automation scenarios. Once connected, you can trigger outbound calls from a Make scenario, pass contact information into your Kickcall AI agent, and pull call details back to decide what happens next.
What you can build: lead follow-up, lead qualification, appointment reminders and confirmations, patient or customer follow-up, no-show recovery calls, and any other scenario-based phone automation across your connected CRM, form tool, or database.
Step 1: Connect Kickcall to Make
Before you build a phone call scenario, connect your Kickcall account to Make. 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 Make connection.
Important: Treat your API key like a password. Never share it publicly or include it in screenshots, shared scenarios, or documentation.
Install Kickcall AI in Make
Open the Make scenario builder and open (or create) the scenario you want to add Kickcall to.
Click the + icon to add a new module.
Search for Kickcall AI in the app picker.
Select the action you want to configure first - Create Phone Call or Get Call Details.
When prompted to connect an account, choose Add next to the Connection field.
Enter your Kickcall connection details: the API key and the email address associated with your Kickcall account.
Click Save to complete the connection.
Once the connection succeeds, Kickcall modules become available inside any scenario in the same Make team.
Step 2: Create a phone call scenario
Create a Make scenario that will trigger the outbound call. Common triggers include:
A new lead or contact form is submitted (Typeform, webhook, or similar)
A new row is added or updated in a connected spreadsheet or database
A new record is created in your CRM
A record enters a specific stage, list, or tag in a connected tool
A scheduled/recurring trigger - for example, daily appointment reminders
A webhook received from any system Make supports
A simple scenario looks like this: Webhook received → Create Phone Call → Get Call Details → Update record.
Tip: Any Make trigger that makes sense for your business will work. Kickcall is designed to sit inside your existing lead intake, scheduling, and CRM automations.
Step 3: Configure the Create Phone Call module
Open your scenario.
Click the module placeholder after your trigger, or after a filter.
Search for Kickcall and select Create Phone Call.
Fill in the required fields, add optional fields if needed, and click OK to save the module.
Required fields
Location - the Kickcall business location the call is created from. This is a dynamic dropdown that fetches the locations available in your Kickcall account, so you simply pick one from the list.
Agent - the Kickcall AI agent that will handle the outbound call. Once you select a Location, this dropdown populates with the active agents for that location.
To Number - the phone number Kickcall should call. Map this from your trigger data, for example the phone field from an incoming webhook or CRM record.
Important: Before mapping a field into To Number, confirm the source field already includes the country code and is formatted in E.164 - for example +12345678900. If your form or CRM only captures a local 10-digit number, add a text-formatting function before Create Phone Call to prepend the country code and strip spaces, dashes, and parentheses.
Optional fields
LLM Dynamic Variables - pass information from Make into the AI agent's prompt: the contact's name, appointment time, reason for the call, or anything else the agent should know before it speaks. Applies to the Response Engine only. Add each variable as a key/value row.
Metadata - arbitrary key/value pairs for your own reference (for example, an internal customer ID). Not used by the agent - stored on the call record for you to retrieve later.
Both fields use the same key/value row format.
Step 4: Store the Interaction ID
When Create Phone Call runs successfully, Kickcall returns details about the new call, including the Interaction ID - the unique identifier for that call.
Save it against the record it relates to, so you have a reusable reference later:
If your connected CRM or database supports custom fields, create one - for example Kickcall Last Interaction ID.
Add an Update/Set module (or the equivalent for your connected tool) after Create Phone Call.
Map the returned interaction_id into that field.
A typical pattern is: Create Phone Call → Filter (if status = queued) → Update record → store the Interaction ID.
Important: Make sure the Interaction ID is stored successfully before you use it with the Get Call Details module.
Step 5: Retrieve call details
Use the Get Call Details module to pull information about a call you created earlier:
Add a new module after your call step, or in a separate scenario triggered later.
Search for Kickcall and select Get Call Details.
Select the same Location and Agent from the dynamic dropdowns that were used to create the call.
Provide the Interaction ID - if you stored it on the record, map that field back in.
Click OK to save the module.
Step 6: Build your scenario automation
With Create Phone Call and Get Call Details in place, Make's routers and filters do the rest:
Add a Router after Get Call Details to branch on call status - completed, no-answer, failed, or voicemail.
On a completed call, route to an update module to log the outcome and the call summary.
On a no-answer or failed call, route to a retry branch, or hand off to a Slack or email notification for your team.
Use the call summary or intent signals returned by Get Call Details to trigger downstream actions, such as flagging a record for manual review.
A full example looks like this: Trigger → Create Phone Call → Store Interaction ID → Get Call Details → Router (call outcome) → branch action.
Other available modules
List all the Locations - retrieves every location configured on your Kickcall account, useful for building your own selection logic instead of using the built-in dropdown.
Get Agent by Location ID - retrieves every agent under a specific location.
Make an API call - a universal module for calling any Kickcall endpoint directly, for advanced use cases not covered by the modules above.
Troubleshooting
Call failed to initiate - usually an incorrect or unsupported phone number format. Check the number includes a valid country code and is formatted as E.164, and add a text-formatting module before Create Phone Call if needed.
Authentication failed - the Kickcall API key is invalid or expired. Generate a new key in your Kickcall dashboard and reconnect the Kickcall connection in Make.
Agent dropdown is empty or shows a 404 - select the Location field first; Agent only populates once a Location has been chosen, since agents are fetched per-location.
Get Call Details does not return the expected information - the Interaction ID is missing or incorrect. Confirm the ID returned by Create Phone Call was stored before Get Call Details runs.
Scenario runs but no call is placed - an upstream filter condition excluded the record, or the scenario is switched off. Check the scenario's execution history and confirm it's turned on.
If you still need help, submit a ticket to the Kickcall support team and include your Kickcall account email, the Make scenario name, the Kickcall module being used, the Interaction ID, the error message, and a screenshot of the module configuration. That detail lets the team resolve the issue much faster.