Resources · Make integration

Smith.ai Make integrationAutomate Smith.ai with Make.

What if every call your receptionists handle landed where your team works? The Smith.ai Make integration gives you 1 trigger and 3 actions to pass call summaries along and queue callbacks. This page walks you through the connection and a first working scenario.

Try the Smith.ai integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Smith.ai Make integration?

The Smith.ai Make integration links your Smith.ai account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or sends something. Here, the bricks let you pick up new call summaries and put contacts in line for an outbound call.

Call summaries that reach your team on their own. Watch New Calls picks up each new summary Smith.ai writes after a call. Send it to a shared sheet, a chat channel or your CRM with the module of another app, and nobody copies notes by hand anymore.

Fast follow-up on inbound leads. A prospect fills a form on your site, and Call a Contact (Virtual Receptionist) adds that person to the receptionists' outbound call queue. The lead hears back from a human voice without anyone on your side dialing.

Campaign lists that fill themselves. When a deal reaches a given stage in your sales tool, Call a Contact (Outreach Campaign) drops the contact into an outreach campaign, which then calls on the cadence set in Smith.ai.

Know the limits before you start: the only trigger is scheduled, so Make checks for new calls on the scenario's schedule rather than the second a call ends, and there is no search module. For anything else in the Smith.ai API, Make an API Call reuses your connection. If you are still choosing a tool, read our Make review or the n8n vs Make comparison, and the Make training covers scenario building step by step.

Connect

How do you connect your Smith.ai account to Make?

  1. 01

    Generate your API key in Smith.ai

    Open your Smith.ai dashboard, click the gear icon at the bottom left to reach account settings, then press Generate an API Key in the API Key section under Account. Copy the key that appears.

  2. 02

    Add a Smith.ai module in Make

    In your scenario, add any Smith.ai module and click Create a connection. A connection is your Smith.ai account linked to Make once, then reused by every Smith.ai module you add later.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you manage several accounts; the field is optional. Paste your API key, follow the on-screen instructions, and the connection is ready.

First scenario

Build your first scenario with Smith.ai

GoalWhen a new lead comes in from your web form, Make adds that person to the Smith.ai receptionists' outbound call queue.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Pick the trigger of the form tool that collects your leads and connect it.

  2. 02

    Add the Smith.ai action

    Click the + on the right of the form module, search for Smith.ai and choose Call a Contact (Virtual Receptionist). Click Create a connection and paste your API key.

  3. 03

    Map the lead's details

    Fill the module with the contact details from the form module: click inside a field and pick the matching value the form sent. Each lead is one bundle, the item that travels from one module to the next.

  4. 04

    Test with Run once

    Submit a test entry on your form, then click Run once. Make runs the scenario one time and shows the bundle each module received, so you can confirm the contact reached the call queue.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What starts a Smith.ai scenario

1 module starts a scenario when something happens in Smith.ai. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Smith.ai as soon as it happens.

Smith.ai1Watch New Calls

Watch New Calls

Scheduled trigger

In Make“Triggers when a new call summary is created.”

Each time Smith.ai finishes a call summary, this trigger hands it to your scenario as a fresh bundle, ready to be logged, shared or turned into a task. It is the only way a Smith.ai event can start a scenario.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan, so a summary can wait until the next check.
When to use it
your sales team wants every inbound call recorded in the CRM without reading emails from the receptionists.
Watch out
since it polls, it is not a live alert; if a caller needs a reply within minutes, pick a paid plan with a shorter interval.
Modules

What Smith.ai can do in a scenario

Smith.ai gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Smith.ai1

Call a Contact (Outreach Campaign)

Action

In Make“Adds a contact to an outreach campaign. The contact will be called using the Outreach Campaign campaign cadence.”

Put a person on the call list of one of your outreach campaigns, and Smith.ai calls them following the cadence that campaign already uses. You feed the list, the campaign does the dialing.

When to use it
a webinar sign-up or a trial account should lead to a planned sequence of calls rather than a single callback.
Watch out
the rhythm comes from the campaign settings in Smith.ai, not from Make; adjust it there.
Smith.ai2

Call a Contact (Virtual Receptionist)

Action

In Make“Adds a contact to the virtual receptionist outbound call queue.”

Get a one-off callback from a live receptionist: the module places your contact in the virtual receptionist outbound call queue. That suits a single, prompt follow-up.

When to use it
a quote request lands on your site and the prospect expects a person to call back.
Watch out
Make only adds the contact to the queue; the call itself is handled on the Smith.ai side, so test with your own details first.
Smith.ai3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach a part of the Smith.ai API that the three ready-made modules leave out, reusing the connection you already created. You write the request yourself, following the Smith.ai API documentation.

When to use it
your process needs an endpoint that neither Watch New Calls nor the two call modules cover.
Watch out
Make builds none of the fields for you here, so read the vendor docs before mapping anything.
Need help

Need help automating Smith.ai with Make?

A person reads every message.

FAQ

Smith.ai and Make: common questions

01Is the Smith.ai Make integration free?
Yes, on the Make side. Smith.ai is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes and includes 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your Smith.ai subscription is separate and is not covered by Make.
02What do you need to connect Smith.ai to Make?
An active Smith.ai account and its API key. In the Smith.ai dashboard, the gear icon at the bottom left opens account settings, where the Generate an API Key button sits in the API Key section. In Make, add a Smith.ai module, click Create a connection, optionally name it, then paste the key. That single connection then serves every Smith.ai module in all your scenarios. Keep the key private, since anyone holding it can act on your account.
03Does the Smith.ai trigger in Make react in real time?
No. Watch New Calls is a scheduled trigger: Make asks Smith.ai for new call summaries on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap between two runs; paid plans go down to 1 minute. Smith.ai has no instant trigger in Make, so a summary created right after a check waits for the next one. If speed matters, the paid plans are the lever to pull, not a setting on the Smith.ai side.
04What if a Smith.ai module is missing in Make?
Use Make an API Call. It calls any endpoint of the Smith.ai API with the connection you already set up, so you are not limited to the trigger and the two call actions. You build the request from the Smith.ai API documentation. The Make documentation for this app is marked as AI-generated from vendor material, so check important details with Smith.ai directly before relying on them. Your scenario can also mix it with the ready-made modules in the same flow.
05Should you use Make or n8n for Smith.ai?
It depends on the tool your team already runs. On Make, Smith.ai offers four ready modules, one scheduled trigger and three actions including Make an API Call, all usable from the Free plan with no code. n8n often has a node for the same app, so check its catalog before switching. Pick the platform where you already maintain your other scenarios; the comparison page on this site sets the two side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations