Resources · Make integration

Circleback Make integrationAutomate Circleback with Make.

Every time a Circleback automation fires, Make can pick up the request and carry it into the rest of your stack. The Circleback Make integration has a single instant trigger. This guide shows how to connect it, build a first scenario and test it before switching it on.

Try the Circleback integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Circleback Make integration do?

The Circleback Make integration lets an automation you set up in Circleback call Make directly. Make then starts a scenario, the automation you build in Make as a chain of modules, and hands the data from that request to whichever app comes next.

The whole integration rests on one module, Watch Webhook Request. A module is one brick of a scenario, and this one is an instant trigger: Circleback calls Make through a webhook as soon as its automation runs, so there is no polling clock to wait on. Everything after it comes from other apps or from Make's own tools.

Three setups follow naturally. A sales lead can send each request to a spreadsheet so the team keeps one running log; an Airtable Make integration works well as that destination. An operations manager can route the request to a CRM record, the way the Agile CRM Make integration does. A project lead can turn it into a message for the people who need to act on it.

Know the limits before you start. Circleback has no action or search module in Make, so Make cannot write back into Circleback or look anything up there. Make also flags that its documentation for Circleback is limited, because little public information about the app is available. Expect to learn the exact shape of the data by running a test.

Many apps also have an n8n node, so check whether Circleback does. If you are weighing the two tools, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect Circleback to Make?

  1. 01

    Add the Circleback module

    Open your scenario, click the + and search for Circleback. Pick Watch Webhook Request, then click Create a connection. A connection is your Circleback account linked to Make once and reused afterwards.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps once several accounts are linked. Then authorize Make on the Circleback page that opens, or paste the key Circleback gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and every scenario that uses Circleback will offer it in the same list, so this step happens only once per account.

First scenario

Build your first scenario with Circleback

GoalWhen a Circleback automation sends a request, Make receives it and passes the data to the app you choose.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas to place the first module.

  2. 02

    Place the Circleback trigger

    Search for Circleback, choose Watch Webhook Request and select the connection you created. This module is what starts every run of the scenario.

  3. 03

    Add the next module

    Click the + on the right of the trigger and pick the app that should receive the data, such as a sheet or a chat tool. Map the fields it needs from what the trigger outputs.

  4. 04

    Test with Run once

    Click Run once, then make your Circleback automation fire. Open the bubble above each module to read the bundles it received; a bundle is one item passed from one module to the next.

  5. 05

    Switch it on

    When the test looks right, turn the scenario on. Because the trigger is instant, Make starts a run whenever Circleback calls it rather than on the default 15-minute schedule.

Triggers

What starts a Circleback scenario

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

Circleback1Watch Webhook Request

Watch Webhook Request

Instant trigger

In Make“Triggers on webhook requests from automations in Circleback.”

You get a scenario that starts the moment one of your Circleback automations sends a request to Make, with the content of that request ready to map into the next module.

How it fires
instant, Circleback calls Make through a webhook as soon as its automation runs.
When to use it
any time you want something Circleback produces to land in another tool without copying it by hand.
Watch out
Make's documentation for this app is limited, so run the scenario once and inspect the bundle before mapping fields you have not seen.
Need help

Need help automating Circleback with Make?

A person reads every message.

FAQ

Circleback and Make: common questions

01Is the Circleback Make integration free?
Yes. Circleback is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer, with at least 15 minutes between scheduled runs. Each module run on one bundle counts as one operation against your monthly credits. Paid plans such as Core, Pro, Teams and Enterprise lift those limits, for example unlimited active scenarios and 40 minutes of execution.
02What do you need to connect Circleback to Make?
A Circleback account and a Make account. Make's documentation lists no specific prerequisite for this app, so the generic connection flow applies: add the Circleback module, click Create a connection, optionally name it, authorize Make on the Circleback page or paste the key it provides, then click Save. The connection is stored once and reused by every Circleback module in your scenarios. If authorization fails, open Make's troubleshooting guidance and check that the Circleback account you used is the right one.
03Does the Circleback trigger in Make fire in real time?
Yes. Watch Webhook Request is an instant trigger, which Make shows with a lightning badge. Circleback calls Make through a webhook as soon as its automation runs, so the scenario does not wait for a polling schedule. That is different from scheduled triggers, which Make checks every 15 minutes by default. Turn the scenario on after testing, otherwise incoming requests will not start a run. Because Make's documentation for this app is limited, run one test and read the bundle to see exactly what arrives.
04What if the Circleback module you need is missing in Make?
It depends on what you need. Circleback offers only one trigger in Make and no Make an API Call module, so Make cannot send data back to Circleback or search it. The usual workaround is to let the trigger feed another app that has the actions you want. If the gap blocks a real project, the team can look at the setup with you. Before looking elsewhere, run a test and check whether the data already in the bundle covers what you had in mind.
05Should you use Make or n8n for Circleback?
It depends on the scenario around Circleback more than on Circleback itself. In Make, the integration is a single instant trigger, so your choice mostly comes down to which tool already connects the apps that receive the data. Many apps also have an n8n node, so first check whether Circleback is one of them. Compare the modules each side offers for your destination apps, and pick the one where your team already builds. Whichever you choose, start with a small test and check the incoming data before you build the rest of the flow.
Same platform

Other docs you might need on this stack.

Browse all integrations