Resources · Make integration

PreCallAI Make integrationAutomate PreCallAI with Make.

Want a PreCallAI call to go out on its own when a lead shows up somewhere else? The PreCallAI Make integration gives you 3 action modules that place calls from a scenario. This guide is for teams that already use PreCallAI and want to wire it to the rest of their tools without code.

Try the PreCallAI integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PreCallAI Make integration let you automate?

The PreCallAI Make integration links your PreCallAI account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that reads or does something in one app. PreCallAI brings three action modules to that chain, so a call can start as a result of something that happened in another tool.

Call a lead through an existing campaign. When a prospect fills in a form or lands in your CRM, the Make Phone Call with Campaign module, judging by its name, hands that contact to a PreCallAI campaign you already set up. You keep the campaign you designed in PreCallAI instead of rebuilding it in Make.

Try a call before it goes live. The Make Phone Call with Playground module, as its name points to, ties the call to the PreCallAI playground. It suits the phase where you still adjust how the agent talks, before plugging a real campaign into your flow.

Reach what the menu does not show. Make an API Call sends a request to any endpoint of the PreCallAI API through the same connection, which covers needs the two call modules leave aside.

What Make does not give here: no trigger. PreCallAI cannot start a scenario on its own, so the flow opens on another app or on Make's clock. The PreCallAI documentation in Make is itself marked as AI-generated, so check anything important with PreCallAI directly. If you weigh the other big automation tool, the n8n vs Make comparison lays out the criteria, and Make pricing explains how operations are counted.

Connect

How do you connect PreCallAI to Make?

  1. 01

    Copy an API key from PreCallAI

    In PreCallAI, click the arrow next to your username and email in the bottom left corner, pick Integrations, then Rest API. Add a new API key and copy the one shown on screen. You need an active PreCallAI account for this.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you run several PreCallAI accounts; the field is optional. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with PreCallAI

GoalWhen a new lead arrives in another app, Make hands that contact to a PreCallAI campaign that places the call.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since PreCallAI has no trigger, this first brick comes from the app where your leads land.

  2. 02

    Pick the starting app

    Search that app by name, choose the module that picks up new leads, and connect the account. Each new lead then travels as a bundle, one item passed from module to module.

  3. 03

    Add the PreCallAI call

    Click the + to the right of the first module, search PreCallAI and pick Make Phone Call with Campaign. Create the connection with your API key, then map the lead data the module asks for from the previous bundle.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Read the bundles each module received and confirm the right contact reached PreCallAI.

  5. 05

    Schedule and switch on

    Set the clock on the first module, which checks every 15 minutes by default, and turn the scenario on. Each module run counts as one operation on your Make plan.

Modules

What PreCallAI modules can do in Make

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

PreCallAI1

Make Phone Call with Campaign

ActionIn the docs only

Going by its name, this action ties an outgoing call to a campaign already set up in PreCallAI, so the setup you tuned there does the talking. There is no official description, so open the module to see which inputs it expects.

When to use it
a contact reaches your pipeline in another app and should be called with a script you already validated.
Watch out
run it once on a test contact before switching the scenario on, because the module places an actual phone call to that number.
PreCallAI2

Make Phone Call with Playground

ActionIn the docs only

Pick this one when you want the call tied to the PreCallAI playground rather than to a finished campaign; that link to the playground comes from the module name, as no official description exists yet. It keeps experiments apart from your live campaign.

When to use it
you are still shaping the agent and want to hear a call triggered by real scenario data.
Watch out
the module name is the only hint about its role, so confirm with PreCallAI how playground calls differ before relying on them.
PreCallAI3

Make an API Call

ActionIn the docs only

Here you reach any endpoint of the PreCallAI API from inside the scenario, reusing the connection you already created. It is the way out when the two call modules do not cover what you need.

When to use it
a PreCallAI feature exists in the API but has no dedicated module in Make.
Watch out
you describe the request yourself, so keep the PreCallAI API documentation open while you set it up.
Need help

Need help automating PreCallAI with Make?

A person reads every message.

FAQ

PreCallAI and Make: common questions

01Is the PreCallAI Make integration free?
Yes on the Make side. PreCallAI is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and lift the active scenario cap. Usage is counted in operations each month. PreCallAI itself needs an active account, and its plans sit on the PreCallAI pricing page.
02What do you need to connect PreCallAI to Make?
An active PreCallAI account and an API key. In PreCallAI, click the arrow beside your username in the bottom left corner, open Integrations, then Rest API, add a key and copy it. In Make, add a PreCallAI module, click Create a connection, optionally fill in Connection name, and paste the key. That single connection then serves all three PreCallAI modules, including Make an API Call, so there is nothing else to set up when you add more of them later.
03Can a PreCallAI event start a Make scenario in real time?
No, because PreCallAI has no trigger module in Make. The scenario has to start somewhere else: on a trigger from another app, such as the form tool or CRM where your leads arrive, or on Make's own schedule, set on the first module and every 15 minutes by default. PreCallAI then comes in as an action further down the chain. On the Free plan, scheduled runs are spaced at least 15 minutes apart; paid plans go down to 1 minute.
04What if a PreCallAI feature is missing from the Make modules?
Use Make an API Call. It sends a request to any endpoint of the PreCallAI API with the connection you already have, so you are not limited to the two call modules. You write the request yourself, so the PreCallAI API documentation becomes your reference. Note also that the PreCallAI page in the Make documentation is flagged as AI-generated and may contain mistakes; for anything important, confirm with PreCallAI directly before relying on it in a live scenario.
05Should you use Make or n8n with PreCallAI?
It depends on the tool your team already runs. On Make, PreCallAI offers three action modules, one connection by API key, and Make an API Call for the rest; you start the flow from another app or from a schedule. The same app often exists as an n8n node too, so check what is available there before choosing. Base the decision on the modules you need and where your other automations already live, rather than on a general ranking of the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations