Can you connect Cirqll to Make.com?

Yes. Cirqll has a REST API based on OAuth2 and JSON, and supports webhooks for almost every part of the system: customers, contacts, deals, appointments, tasks, contracts and more. Make can work with both.

One thing to know: at the time of writing (28 September 2026) we did not find a ready-made Cirqll app with its own modules in Make. Cirqll itself lists Zapier as its standard automation integration. In Make you therefore build the integration from two generic building blocks:

  • A webhook module that receives messages from Cirqll. In Cirqll you choose which events (topics) to send to that webhook, for example a new appointment or a changed deal.
  • An HTTP module that calls the Cirqll API through an OAuth2 connection, to fetch or create data.

That sounds more technical than a ready-made app, and it is a little. The upside is that you are not limited to the handful of actions a standard app offers: anything the API can do, you can use. How Make compares with n8n is explained in Make vs n8n.

Which 5 Cirqll automations should you set up first?

Start with processes that happen often, always run the same way and currently cost time or get forgotten. For most Cirqll users, these five are a logical place to begin.

1. New website leads straight into Cirqll

Someone fills in the contact form on your site. Make receives the data, checks in Cirqll whether the customer already exists, and otherwise creates a new customer and contact. Make then sets up a task for the right colleague: "call this lead within one working day". No more retyping from your mailbox, and no lead sitting in someone's inbox for a week.

2. An alert and follow-up steps when a deal reaches the final stage

In Cirqll you name the stages of a deal yourself, such as "In negotiation" or "Verbal agreement". With a webhook on deal changes, Make sees when a deal moves to the stage that means "agreed" for your team. Make then posts a message to the team in Teams or Slack and creates the standard follow-up tasks, such as sending an order confirmation or scheduling a kick-off.

3. Preparing and following up appointments

A new appointment is created in Cirqll. Make fetches the customer and their open deals and emails the account manager a short briefing. After the appointment, Make creates a task to record the meeting notes. However good your team is, this is exactly the kind of work that slips in a busy week.

4. Picking up contracts that are about to expire in time

Contracts in Cirqll have a start and end date. A Make scenario that runs every morning requests the contracts whose end date falls within, say, 60 days. For each contract without an open task, Make creates a task for the owner, so renewing or renegotiating becomes a planned action instead of a surprise.

5. A weekly pipeline summary in your inbox

Every Monday morning Make fetches the open deals, adds up the value per stage and sends an overview to the sales team: how much is open, what was added last week, which deals have been idle for a long time. For a first view that is enough. If you want to see trends, win rates and cycle times, a dashboard is the better place. How that works is explained in Connecting Cirqll to Power BI.

How does a Cirqll integration in Make work technically?

You do not need to be a programmer to follow this, but a few things decide whether your integration runs reliably.

  • Webhooks instead of asking over and over. Cirqll itself recommends using webhooks rather than checking every minute whether something has changed. That suits Make too: a scenario that checks every minute uses credits even when nothing has happened. A webhook only runs when there is actually something to do.
  • Topics per resource. A webhook listens to events such as creating, updating or deleting a specific resource. There is no wildcard for "everything", so you consciously choose the events you need.
  • OAuth2 with expiring tokens. Cirqll access tokens expire after 15 days and refresh tokens after 30 days. A properly configured OAuth2 connection in Make refreshes them automatically. If it does not, your integration stops after two weeks without warning.
  • A maximum of 100 requests per minute. Cirqll applies a limit of 100 API requests per minute per client. For a large import or a scenario that loops through hundreds of records, build in a pause or batching.

Example: from web form to follow-up task

A fictional example to make it concrete. An installation company with two sales people receives leads through the quote form on its website. Until now the form arrives as an email, someone retypes the details into Cirqll and the lead is assigned when there is time.

The Make scenario looks like this:

  1. Trigger: the form sends its data to a webhook in Make.
  2. Search: Make asks the Cirqll API whether a customer or contact with this email address or company name already exists.
  3. Create or update: if the customer does not exist, Make creates the customer and contact. If it does, Make adds a note with the new request.
  4. Assign: based on the postcode, Make decides which sales person gets the lead.
  5. Task: Make creates a task in Cirqll for that sales person, including the question from the form.
  6. Error handling: if something goes wrong, for instance because Cirqll is briefly unavailable, a fixed colleague receives an email with the form details. That way no lead ever gets lost.

The result: every request is in Cirqll within a minute, with the right person, with a task attached. The retyping disappears and nobody has to keep track of who has which lead.

What should you check before you start?

  1. Clean up your data first. If the same customer is in Cirqll three times, an automation will happily add a fourth. Decide how you recognise an existing customer, for example by email address or Chamber of Commerce number.
  2. Use a dedicated user with limited permissions. Do not connect Make through the managing director's account, but through a user that can only do what the integration needs.
  3. Build in error handling from day one. A scenario that fails silently is worse than no scenario, because everyone assumes it works. Have Make send an alert when a step fails.
  4. Document what is running. A short list of which scenarios exist, what they do and who owns them saves a lot of searching when something changes a year from now.
  5. Keep the GDPR in mind. Personal data flows through the integration. Record which data goes where and choose EU hosting where possible.

How to decide which processes to automate first is covered in workflow automation: the first processes.

Help with your Cirqll automations in Make

Want these automations set up without working with APIs and tokens yourself? We build Make scenarios that fit your Cirqll setup, with error handling and documentation. See what we do in workflow automation, read more about our Cirqll integration with Power BI or see which other integrations we build.