Resources · Make integration

Channels Make integrationAutomate Channels with Make.

Can your phone support tool keep its contact list in sync without anyone copying names by hand? The Channels Make integration gives you 7 modules: one trigger on incoming call status, five contact and API actions, one search. This page shows how to plug in your account and build a first scenario that works.

Try the Channels integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Channels Make integration let you automate?

The Channels Make integration links your Channels account to Make, a visual tool where you build a scenario (the automation itself, a chain of steps) without code. Each step is a module: it can watch incoming call status, or read, create, change and delete the contacts your support team calls.

A contact book that fills itself. A lead lands in your form tool or CRM, and Create a Contact adds that person to Channels before they ever dial in. Your agents see a name instead of a bare number.

Clean records when something changes. A customer updates their details in your billing app: Update a Contact rewrites the Channels entry, and List Contacts helps you find the right one first. Delete a Contact handles the opposite case, when an account is closed.

A reaction to your calls. Watch Incoming Call Status starts the scenario when the status of an incoming call changes, so you can pass that event to a helpdesk, a chat tool or a spreadsheet. Get a Contact can then fetch a record your team needs next to it.

What Make does not cover here: only these 7 modules are listed, and the Make documentation for Channels is flagged as AI-generated, so verify anything important with Channels. For the rest of its API, Make an API Call reuses the same connection. The same app sometimes has an n8n node too; the n8n vs Make comparison lays out how the two tools differ, Make pricing explains what operations cost, and Make training takes you further once this first scenario runs.

Connect

How do you connect your Channels account to Make?

  1. 01

    Copy your API key and account

    In Channels, click your Account icon in the top right corner, open the Developer tab, then the API section. Copy the API key shown there, and copy the Account value right next to it. Make needs both.

  2. 02

    Add a Channels module in Make

    In your scenario, add any Channels module and click Create a connection. The Connection name field is optional; a clear name like the team or the workspace helps when you run several accounts.

  3. 03

    Paste the credentials and save

    Paste the API key and the Account you copied, then save. That connection (your Channels account linked to Make once) is reused by every Channels module you add later, so you only do this step one time.

First scenario

Your first scenario: new lead in, Channels contact out

GoalWhen a new lead arrives in the app where you collect them, Make creates the matching contact in Channels.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the module of the app where your leads land, such as your form tool or your CRM.

  2. 02

    Add Create a Contact

    Click the + on the right of that first module, search for Channels and choose Create a Contact. Select the connection you built earlier, or click Create a connection now.

  3. 03

    Map the lead data

    Fill the fields Make shows for the new contact by clicking into each one and picking the matching value from the first module. Nothing is typed by hand: the lead flows straight across.

  4. 04

    Test with Run once

    Send a test lead, then click Run once. Read the bundles each module received (one bundle is one item, here one lead) and check the contact in Channels.

  5. 05

    Schedule and switch on

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

Triggers

What can start a Channels scenario?

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

Channels1Watch Incoming Call Status

Watch Incoming Call Status

triggerIn the docs only

This trigger gives you a scenario that reacts to your phone line: whenever the status of an incoming call changes in Channels, Make picks it up at its next check and the next modules can act on it.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up what changed since the last check.
When to use it
pick it when a call should leave a trace somewhere else, like a ticket in your helpdesk or a line in a shared sheet for the support lead.
Watch out
the Make directory was unavailable for this app, so the scheduled type comes from the module name. Look for the clock badge on the module in your editor to confirm it.
Modules

What can Make do in Channels?

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

Channels1

Get a Contact

ActionIn the docs only

You get the record of one Channels contact inside your scenario, ready to pass its details to the next module, whether that is an email tool or a ticket.

When to use it
after a search or another app's module, when you already know which contact you want and need its details for the next step.
Watch out
it reads a single contact you point to. If you only have a partial clue, run List Contacts first to find the right one.
Channels2

List Contacts

SearchIn the docs only

Returns the contacts stored in Channels, one bundle per person, so the modules after it can process each one in turn or check whether someone already exists.

When to use it
before creating a contact from a new lead, to avoid adding the same caller twice.
Watch out
as a search, it can hand back zero, one or many bundles. Every module placed after it runs once per bundle, and each run is an operation.
Channels3

Create a Contact

ActionIn the docs only

Adds a new person to your Channels contact list from data that comes out of another app, so your agents see a real name the first time that customer calls.

When to use it
when a lead signs up through a form, or a deal closes in your CRM and the customer now needs phone support.
Watch out
nothing stops a duplicate on its own. Put a List Contacts step and a filter before it if the same person can show up twice.
Channels4

Delete a Contact

ActionIn the docs only

Removes a contact from Channels for good, which keeps your agents from calling people who asked to leave or whose account was closed elsewhere.

When to use it
when a customer cancels in your billing tool or asks to be erased, and Channels should follow that decision.
Watch out
play it safe and treat a deletion as final. Test it with Run once on a dummy contact before pointing it at real data.
Channels5

Make an API Call

ActionIn the docs only

Opens the rest of the Channels API to your scenario, using the same connection as the other modules, for any job the six ready-made modules leave out.

When to use it
when you need an action on something other than contacts or call status and the Channels developer documentation describes it.
Watch out
here you work with the raw API, so you read the Channels documentation yourself to know which request to send.
Channels6

Update a Contact

ActionIn the docs only

Rewrites the details of an existing Channels contact so the record your agents open during a call matches what the customer just changed in another tool.

When to use it
when a customer edits their profile in your shop or CRM and the support team should see the new version.
Watch out
it needs to know which contact to change. Chain it after List Contacts or Get a Contact so the right record is targeted.
Need help

Need help automating Channels with Make?

A person reads every message.

FAQ

Common questions about Channels and Make

01Is the Channels Make integration free?
Yes, on the Make side. Channels is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 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 drop the minimum interval to 1 minute and remove the cap on active scenarios. You still need an active Channels account, whose subscription is set by Channels itself.
02What is needed to connect Channels to Make?
An active Channels account and its API key. The key sits in the developer area: click the Account icon at the top right of Channels, open the Developer tab, then the API section, and copy the API key along with the Account value. In Make, add a Channels module, click Create a connection, give it a name if you like, and paste both values. After that, every Channels module in your scenarios reuses this connection.
03Does the Channels trigger react in real time?
No. Watch Incoming Call Status is listed as a scheduled trigger: Make checks Channels on the scenario's schedule instead of being called the moment a status changes. A new scenario checks every 15 minutes by default. On a paid plan you can shorten that interval down to 1 minute. Since the type was read from the module name, check for the clock badge on the module in the editor to confirm it before relying on the timing.
04What if a Channels module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Channels API with the connection you already set up, so you are not stuck with the 7 listed modules. You do need to read the Channels API documentation to build the request. One more point: the Make documentation page for Channels says it was generated with AI and may contain mistakes, so double check key details with Channels before building something critical.
05Should Channels be automated with Make or n8n?
It depends on the tool your team already runs. Many apps exist on both, so check whether Channels has an n8n node before deciding. In Make, you get the 7 modules described here, a visual editor where each step shows the bundles it received, and Make an API Call for anything not covered. If your other automations already live in one of the two tools, that is a fair criterion to weigh first.
Same platform

Other docs you might need on this stack.

Browse all integrations