Which Cirqll integrations are there?

Cirqll is built to talk to other systems. On its own site (as of 15 October 2026) Cirqll mentions integrations with the Dutch Chamber of Commerce (KVK), Outlook and Google, among others, and connections with accounting and ERP packages such as Exact Online, AFAS, Ridder iQ, 4PS and Business Central, and with email tools such as Mailblue, ActiveCampaign and Mailchimp. How each of those connections is built differs per package. Cirqll itself says data can be exchanged through Zapier, through the API or through integration specialists.

For you as a user it comes down to four routes:

  • Zapier. Cirqll has its own Zapier app. You click an integration together without code.
  • Make.com with the Cirqll API. More steps, conditions and error handling, but a bit more setup.
  • Your own integration on the API. A script, cloud function or database that talks to Cirqll directly.
  • A ready-made connector. For reporting in Power BI there is the Cirqll Power BI Connector, with a dashboard template included.

Want to know first what the API can do technically? Read Cirqll API: what you can do with it and what you need. This article is about the choice: which route fits your question?

Which integration suits which system?

Most integrations fall into five groups. For each group a different route tends to come back in practice.

Website and forms

A request through your site needs to arrive in Cirqll as a customer, contact or deal, with a follow-up task. For a simple form Zapier is enough. If you want to check first whether the customer already exists, assign leads by region and get an alert when something goes wrong, Make.com is the better place. A worked example is in Cirqll and Make.com: 5 automations.

Email and calendar

Cirqll itself mentions integrations with Outlook and Google. Check what is included as standard before you build anything yourself. An extra integration is only needed if you want more than syncing, such as automatically sending a briefing before an appointment.

Email marketing

Automatically adding new customers or contacts to a mailing list is a classic one-way integration: from Cirqll to your email tool. Zapier often handles that fine. Mind consent: not everyone in your CRM wants your newsletter.

Accounting and ERP

This is where most of the risk sits, because data often flows in both directions. A won deal becomes a customer in your accounting, and a quote in your ERP becomes a deal in Cirqll. Agree per data item which system is leading. If Cirqll mentions an integration for your package, start there. Otherwise Make.com or your own integration is the route.

Reporting

For dashboards you do not want to pass on individual events, but fetch all data at a fixed moment and build up history. Zapier and Make are not made for that. A connector or your own data layer is the logical choice here. How to build such a dashboard is explained in Connecting Cirqll to Power BI.

Zapier or Make.com: which do you choose for your Cirqll integration?

Both are no-code automation platforms. The difference is in what you can do with them for Cirqll.

Zapier has a Cirqll app with triggers for new events, for example a new customer, deal, task, appointment, note or contract. You can also create customers, contacts, deals, tasks and notes, among others, update some resources and search for records. For "when this happens, do that" this is more than enough.

Make.com has no ready-made Cirqll app as of 15 October 2026. You work with a webhook module that receives messages from Cirqll and an HTTP module that calls the Cirqll API through OAuth2. That takes more setup, but you can use everything the API offers, with multiple steps, conditions, loops and error handling.

Our rule of thumb:

  • One trigger and one or two actions, without exceptions? Zapier.
  • Searching before creating, deciding based on data, several systems in one flow, or an alert when something goes wrong? Make.com.

More on the differences between platforms in Make vs n8n.

How do you choose the right Cirqll integration? A step-by-step plan

Five questions, in this order. If you answer them up front, you usually only build the integration once.

  1. What needs to happen, in one sentence? For example: "Every won deal becomes a customer in the accounting system." If you cannot write that sentence, the question is not sharp enough yet.
  2. Which way does the data go? One direction is simple. Two directions requires agreements about which system is leading per field, otherwise the systems overwrite each other.
  3. Per event or in bulk? If something must happen as soon as something changes in Cirqll, you work with triggers or webhooks. If you want to fetch everything at a fixed moment, for example for reporting, a scheduled integration or connector is better.
  4. Does a route already exist? First check whether Cirqll mentions an integration for your package, whether Zapier can do it, or whether a connector exists. Only then Make.com, and only after that building it yourself.
  5. Who manages it? Every integration needs an owner: someone who gets an alert when it goes wrong and knows what is running. Without an owner, an integration sooner or later stops without anyone noticing.

Example: three integrations, three routes

A fictional example to make it concrete. A consultancy with six employees works in Cirqll and wants to connect three things.

  • New contacts to the newsletter list, if they have given consent. One direction, one trigger, one action. That becomes a Zap.
  • Quote requests from the website into Cirqll, with a check for existing customers, assignment to two consultants and an email to the office manager if the integration fails. That becomes a Make scenario with a webhook, HTTP modules and an error handler.
  • A monthly report with won deals per consultant and the value of running contracts, including previous years. That becomes Power BI with a connector, because it is about all data and history, not individual events.

For all three, the consultancy creates a separate Cirqll user with only the permissions needed, and keeps one short list of what is running, what it does and who owns it.

Where does a Cirqll integration usually go wrong?

  • Expired tokens. An integration through the API uses OAuth2. An access token is valid for 15 days and a refresh token for 30 days. If the integration does not refresh them automatically, it stops after a few weeks without warning.
  • The limit. Cirqll allows a maximum of 100 API requests per minute per client. A first large import or a loop through hundreds of records easily hits that. Build in pauses or batches.
  • Duplicate customers. An integration that does not search first creates a new customer for every request. Agree how you recognise an existing customer, for example by email address or Chamber of Commerce number.
  • Silent failure. An integration that stops without an alert is worse than no integration, because everyone thinks it works. How to prevent that in Make is covered in Make.com error handling.
  • Personal data. Customer data flows through the integration. Record which data goes where and choose EU storage where possible.

Help with your Cirqll integration

Not sure which route fits your situation, or want the integration built with error handling and documentation included? Take a look at the Cirqll Power BI Connector and dashboard template, see what we do in workflow automation and data engineering, or check which other integrations we build.