Resources · Make integration

Callin.io Make integrationAutomate Callin.io with Make.

Can Make react to your Callin.io calls and start an agent for you? The Callin.io Make integration gives you 2 modules: one trigger that picks up transcriptions and one action that activates an agent. This page shows you how to link your account and build a first working scenario.

Try the Callin.io integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Callin.io Make integration let you automate?

The Callin.io Make integration links your Callin.io account to Make, a no-code tool where you build a scenario, meaning the automation itself, out of modules, the building blocks of that chain. With it, Make can pick up transcriptions from Callin.io and activate one of your agents when something happens in another app.

Start an agent the moment a lead appears. A sales team collects leads through a web form. The form app opens the scenario, and Activate an Agent sets a Callin.io agent in motion for that new contact, with no one copying details by hand.

Send every transcription where your team reads it. Watch Transcription hands each new transcription to the next module, which can post it to a chat channel, store it in a spreadsheet or attach it to a CRM record. A support lead then reviews calls without logging in to Callin.io.

Chain both sides with other tools. The two modules fit different moments: one listens to what Callin.io produces, the other asks Callin.io to act. You can combine each of them with any of the other apps Make supports; the Make training walks through that kind of build step by step.

Keep the scope in mind. The app has no search module and no universal API call module, so anything beyond these 2 modules is out of reach here. The official doc also warns that its content is AI-generated from Callin.io documentation and may contain mistakes, so confirm important details with Callin.io. If you also look at n8n, the n8n vs Make comparison explains how the two tools differ.

Connect

How do you connect your Callin.io account to Make?

  1. 01

    Copy your API key in Callin.io

    Sign in to Callin.io, open the profile section and click API Keys. Copy the key shown on screen. You need an active Callin.io account for this; the key is what lets Make act on your behalf.

  2. 02

    Add a Callin.io module in Make

    In your scenario, add any Callin.io module and click Create a connection. A connection is your Callin.io account linked to Make once, then reused by both modules of the app.

  3. 03

    Name the connection and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste the API key you copied, or follow the instructions Make displays, then save.

First scenario

Build your first scenario with Callin.io

GoalWhen a new lead reaches another app, Make activates a Callin.io agent for that contact.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. It will be the trigger of the app where your leads land, such as a form tool.

  2. 02

    Set up the lead source

    Search for that app by name, pick its trigger and link its account. Fill in its fields; once the connection exists, Make lists the forms or objects it can read for you.

  3. 03

    Add Activate an Agent

    Click the + on the right of the first module, search for Callin.io and choose Activate an Agent. Select your connection, then map the lead data coming from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once and submit a test lead. Each module shows the bundles it received, a bundle being one item passed along, here one lead. Check that the agent did start in Callin.io.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set Scheduling, every 15 minutes by default for a new scenario. Then switch the scenario on so it keeps running without you.

Triggers

What starts a Callin.io scenario

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

Callin.io1Watch Transcription

Watch Transcription

triggerIn the docs only

This trigger brings new Callin.io transcriptions into your scenario, one bundle per transcription, so the rest of the chain can file, share or review what was said on a call.

How it fires
scheduled, Make checks the app on the scenario's schedule, as shown by the clock badge. That type is inferred from the module's name, so look at the badge when you add it.
When to use it
you want every finished call to land in a shared place, like a support channel or a CRM note, without opening Callin.io.
Watch out
on the Free plan the shortest interval between two scheduled runs is 15 minutes, so transcriptions arrive in batches rather than one by one.
Modules

What the Callin.io modules do

Callin.io gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Callin.io1

Activate an Agent

ActionIn the docs only

You get a Callin.io agent started from any event Make can see, whether a new lead, a booked slot or a row added to a sheet, instead of launching it yourself in Callin.io.

When to use it
a contact form is submitted and you want the Callin.io agent started for that person without waiting for anyone to launch it.
Watch out
the official doc gives no description of this action and warns its content may contain mistakes, so run it once with a test contact before switching the scenario on.
Need help

Need help automating Callin.io with Make?

A person reads every message.

FAQ

Callin.io and Make: common questions

01Is the Callin.io Make integration free?
Yes, on the Make side. Callin.io is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Callin.io account with an API key; see Callin.io for its own subscription.
02What do you need to connect Callin.io to Make?
An active Callin.io account and an API key. In Callin.io, open the profile section, click API Keys and copy the key. In Make, add a Callin.io module, click Create a connection, give it a name if you like and paste the key. The connection is then reused by both Callin.io modules, so you only do this once per account. If the key is missing or wrong, the connection fails, so copy it again straight from the API Keys screen rather than from an old note or message.
03Does the Callin.io trigger work in real time?
No. Watch Transcription is a scheduled trigger: Make checks Callin.io on the scenario's schedule, every 15 minutes by default, and never faster than every 15 minutes on the Free plan. On a paid plan you can bring that down to 1 minute. Note that the type was inferred from the module's name, so the clock badge on the module is the reference when you build. If a slower rhythm suits you, keep the default and let the scenario pick up transcriptions in batches.
04What if the Callin.io module you need is missing?
It depends on the need. The app offers only 2 modules, Watch Transcription and Activate an Agent, and has no universal API call module, so you cannot reach other Callin.io features from Make directly. Look for another app in your stack that already holds the data, or ask the team for help designing a workaround. For anything unclear in the doc, contact Callin.io, as the doc itself advises. Before building around a gap, run each module once with test data to see exactly what it returns.
05Should you use Make or n8n for Callin.io?
It depends on the tool you already run. Callin.io may also have an n8n node, and the right pick is usually the platform where your other automations already live. On Make you get the 2 modules described here, a visual editor and a Free plan to test with. This page makes no claim about speed or price between the two; compare them on your own scenario before you commit. The n8n vs Make comparison linked above sets out the differences if you want a closer look.
Same platform

Other docs you might need on this stack.

Browse all integrations