Which Cirqll contract data can you use in Make?

A contract in Cirqll belongs to a customer and has an owner: the user who is responsible for it. According to Cirqll's API documentation (as of 12 October 2026) a contract also has these fields:

  • Name and description: what the contract is about.
  • Start date and end date: the term.
  • Reminder date: an optional date on which someone needs to act on the contract.
  • Price and price type: an amount per month or per year.
  • Archive date: filled in when the contract has been archived.

Through the API you can filter contracts by archive status, customer and date range. That is exactly what you need to ask: "give me all active contracts that expire in the next 60 days". Cirqll also supports webhooks on create, update and delete, so Make gets a signal straight away when something changes on a contract.

How to connect Cirqll to Make in general, with a webhook module and an HTTP module using OAuth2, is explained in Cirqll and Make.com: 5 automations. What else the API can do is covered in Cirqll API: what you can do with it.

Does Cirqll handle invoicing itself?

No. Cirqll is a CRM: you record customers, deals, appointments and contracts in it. Invoices are created in your accounting package. Cirqll's API has no invoice resource either.

That is exactly the problem many companies recognise. The contract lives in Cirqll, the invoice in the accounting system, and in between sits a person who has to remember that a new contract also means a recurring invoice, and that a price increase also has to be applied in the accounting system. When that goes wrong, you invoice late, too little or not at all.

Make can bridge that gap. Many accounting packages have an app in Make. Moneybird, for example, has modules to create contacts and sales invoices, among other things. That way a change in Cirqll can automatically trigger an action in your accounting, or at least an alert to the person who handles invoicing.

Which contract follow-up actions should you automate?

For most companies these five are a logical start. Begin with one, let it run for a few weeks and then build on it.

1. Picking up renewals on time

A scenario that runs every morning requests the active contracts whose end date falls within, say, 90 days. For each contract Make creates a task in Cirqll for the contract owner: "discuss renewal with this customer". If you use the reminder date, Make can act on that too. An expiring contract becomes a planned action instead of a surprise.

2. New contract, alert to bookkeeping

A contract is created in Cirqll. Through a webhook Make sees this immediately, fetches the customer and sends the person who handles invoicing a message with customer, amount, price type and start date. If you want to go further, Make looks up the customer in your accounting package and prepares a draft invoice there. A draft, not sent straight away: someone takes a quick look first.

3. Passing on price changes

The price of a contract is changed, for example after an annual indexation. Make picks up the change and reports the old and new amount to bookkeeping. That way the recurring invoice does not stay on the old amount.

4. Ended or archived contract

When a contract is archived or its end date passes, Make sends an alert: stop the recurring invoice for this customer. Here too, it is best to leave the actual stopping to a person, because sometimes there is still a final instalment.

5. Monthly check: does the contract match the invoice?

Once a month Make puts the active contracts from Cirqll next to the invoices from your accounting system and emails a list of discrepancies: contracts without an invoice, or invoices for customers without an active contract. This is the automation that pays off most, because it finds missed revenue instead of just saving time.

Example: a morning scenario for contract follow-up

A fictional example to make it concrete. An IT service provider with around eighty maintenance contracts records all contracts in Cirqll and invoices in Moneybird. Renewals are picked up when someone happens to remember, and a new contract is passed on to the bookkeeper by email.

The Make scenario that runs every working day at 7:00:

  1. Fetch: Make requests all non-archived contracts through the Cirqll API, including the customer.
  2. Filter: for each contract Make checks the end date and the reminder date. If either falls within 90 days, the contract moves on to the next step.
  3. Avoid duplicates: Make checks whether there is already an open renewal task for this contract. If not, it creates one for the owner.
  4. Summarise: the owner receives one email with all contracts that need attention, sorted by end date, with the amount per month or per year.
  5. Error handling: if a step fails, for instance because Cirqll is briefly unavailable, a fixed colleague receives an alert. A scenario that fails silently is worse than no scenario.

Next to that, a second, smaller scenario runs on a webhook: when a contract is created or changed, the bookkeeper receives a message with the details. The result: renewals are discussed on time and the bookkeeper hears straight away when something changes, without anyone having to remember.

Where does contract automation go wrong?

  • Incomplete contracts. An automation is only as good as the data. If the end date is wrong, or a contract is never archived, you get the wrong alerts. Agree on what a complete contract looks like.
  • Customers you cannot match. To connect Cirqll to your accounting, Make needs to know which customer in one system belongs to which in the other. A name is too weak for that. Record a customer number or Chamber of Commerce number, for example in a custom field in Cirqll.
  • Expiring tokens. A Cirqll access token is valid for 15 days, a refresh token for 30 days. A properly configured OAuth2 connection refreshes them automatically. If it does not, your scenario stops without warning.
  • The limit of 100 requests per minute. With a few hundred contracts and an extra request per contract you hit that quickly. Load customers together with the contracts in one request and build in a pause where needed.
  • Time zones. Cirqll returns dates in UTC. An end date at midnight Dutch time can look like the previous day in UTC. Account for that in Make.
  • Wanting to send too much automatically. Let Make prepare invoices as drafts and send alerts, but leave sending to customers to a person at first.

What if you mainly want an overview?

Make is strong at action: tasks, alerts, draft invoices. If you mainly want to see how much recurring revenue is in your contracts, how it develops and which contracts expire next quarter, a dashboard is the better place. How to get Cirqll data into Power BI is explained in Connecting Cirqll to Power BI. Combine that with your accounting and you see contract value and invoiced revenue side by side.

Help with automating your Cirqll contracts

Want to automate your contract follow-up without working with APIs, tokens and error handling yourself? We build Make scenarios that fit your Cirqll setup and your accounting package, with documentation included. See what we do in workflow automation, read more about our Cirqll integration with Power BI, take a look at the Moneybird integration or all integrations we build.