Resources · Make integration

Cin7 Make integrationAutomate Cin7 with Make.

Keep Cin7 contacts and payments in step with the rest of your tools, without writing code. The Cin7 Make integration gives you 14 modules: 10 actions and 4 searches. This guide shows you how to link your account, build a first scenario and pick the right module.

Try the Cin7 integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cin7 Make integration do for you?

The Cin7 Make integration links your Cin7 Omni account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that reads or writes data in one app. With it, Make can create, read, update and delete contacts and payments in Cin7, and read branches and product categories.

New customers land in Cin7 on their own. A signup form, a CRM or a spreadsheet sends each new buyer to Create a Contact, so the sales team stops retyping details. When a buyer changes address, Update a Contact fixes the same record in place.

Payments reach your finance tools. List Payments hands every payment to the next module as a bundle (one item that flows from one module to the next), ready to be copied into a sheet or an accounting app. A payment recorded elsewhere can go the other way through Create a Payment.

Reference data stays shared. List Branches and List Product Categories feed other tools with the exact names used in Cin7, which keeps reports consistent.

One thing to know first: Cin7 has no trigger in Make, so nothing starts a scenario from inside Cin7. The scenario starts on its schedule, or on an event in another app. For anything the 14 modules skip, Make an API Call reaches the rest of the Cin7 API. Apps like Cin7 often have an n8n node too; the n8n vs Make comparison helps you choose, and our Make review covers the tool itself. If you would rather learn step by step, see Make training.

Connect

How do you connect Cin7 to Make?

  1. 01

    Create an API connection in Cin7

    In Cin7 Omni, open Settings from the user menu, then API v1 under Integrations & API. Click Add New API Connection, give it a short name such as Make, and copy both the API key and the API Username.

  2. 02

    Add a Cin7 module in Make

    In your scenario, add any Cin7 module and click Create a connection. A connection is your Cin7 account linked to Make once, then reused by every Cin7 module. The Connection name field is optional but helps when you run several accounts.

  3. 03

    Paste your credentials

    Paste the API key and the API Username you copied, or follow the instructions Make shows on screen, then save. The module can now read your Cin7 data, and every later Cin7 module picks this connection from a list.

First scenario

Build your first scenario with Cin7

GoalWhen a new lead arrives in another app, Make creates the matching contact in Cin7.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your leads live first, such as a form or a CRM: Cin7 has no trigger, so the start comes from there.

  2. 02

    Add Create a Contact

    Click the + on the right of the first module, search for Cin7 and choose Create a Contact. Pick your connection, or click Create a connection if this is your first Cin7 module.

  3. 03

    Map the lead details

    Fill the contact fields by clicking the values the first module returns, such as the lead details from your form. Make shows them as soon as that module has received data once.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Each module shows the bundles it received; open the Cin7 one and check that the new contact has the right details before going further.

  5. 05

    Schedule it and switch it on

    Open Scheduling on the first module, keep the default of every 15 minutes or change it, then switch the scenario on. Each module run counts as one operation, the unit Make counts on your plan.

Modules

What each Cin7 module does

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

Cin71

Create a Contact

Action

In Make“Creates a contact.”

Adds a new contact to Cin7 from data that arrives in another app, so a buyer or supplier exists in Cin7 without anyone typing it in.

When to use it
right after a signup form, a CRM deal or a spreadsheet row, when the person is not in Cin7 yet.
Watch out
the module adds a record every time it runs. If the same lead can come twice, check first with List Contacts to avoid duplicates.
Cin72

Create a Payment

Action

In Make“Creates a new payment.”

Records a new payment in Cin7, so money collected in another tool also shows up in Cin7, next to the rest of your customer data.

When to use it
a payment app or a spreadsheet confirms that a customer has paid, and Cin7 should carry that payment as well.
Watch out
run the scenario with Run once on a test case first, then open Cin7 to confirm the payment shows up the way you expect.
Cin73

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a contact from Cin7, which keeps the list clean when a record was created by mistake or a customer asks to be forgotten.

When to use it
a cleanup flow finds duplicates, or a request for removal arrives through a form.
Watch out
treat the deletion as final. Check the record with Get a Contact first, and test on a dummy contact with Run once before switching the scenario on.
Cin74

Delete a Payment

Action

In Make“Deletes a payment”

Removes a payment from Cin7, useful when a payment was recorded twice or cancelled in the tool where it started.

When to use it
a refund or a cancellation in your payment app should remove the matching entry in Cin7.
Watch out
this module changes your financial records. Test it on a dummy payment with Run once, and read the bundle Get a Payment returns before letting it act on real data.
Cin75

Get a Branch

Action

In Make“Retrieves information about specific branch.”

Returns the details of one specific branch of your Cin7 account, so the next modules can reuse its details in a message or a report.

When to use it
you already know which branch matters for this scenario and only need that one, not the whole list.
Watch out
to see every branch at once, List Branches is the better choice.
Cin76

Get a Contact

Action

In Make“Retrieves information about specific contact.”

Fetches the full record of one Cin7 contact, so later modules can use its details in an email, a sheet or another app.

When to use it
a previous module gives you a single contact and you need the rest of its information before acting.
Watch out
it returns one contact only. When you do not know which record you need yet, start with List Contacts.
Cin77

Get a Payment

Action

In Make“Retrieves information about specific payment.”

Reads the details of one payment stored in Cin7, which lets you check a payment before sending it to your accounting tool or a colleague.

When to use it
a scenario already points to one payment, and you want its information before updating it or copying it elsewhere.
Watch out
for a batch of payments, List Payments saves you from calling this module again and again.
Cin78

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Cin7 API with the connection you already set up, which opens up everything the other Cin7 modules leave aside.

When to use it
you need a Cin7 object or action that no listed module covers, and you know which API endpoint to call.
Watch out
this one expects some comfort with APIs. Read the Cin7 API documentation first, then test your request with Run once.
Cin79

Update a Contact

Action

In Make“Updates a Contact by ID.”

Changes an existing Cin7 contact in place, so a new phone number or address typed in your CRM reaches Cin7 too.

When to use it
a record changes in another tool and the same person already exists in Cin7.
Watch out
the module works from the contact ID. Put Get a Contact or List Contacts before it and map the ID from there.
Cin710

Update a Payment

Action

In Make“Updates specific payments by ID.”

Edits a payment already stored in Cin7, which keeps its details aligned when the source changes after the first record.

When to use it
a payment is corrected in your payment app or spreadsheet, and Cin7 should show the corrected version.
Watch out
the payment is found by its ID. List Payments gives you that ID, so place it earlier in the scenario and map it.
Cin711

List Branches

Search

In Make“Lists all branches.”

Returns all the branches set up in your Cin7 account, one bundle per branch, ready to be written in a sheet or used as a reference.

When to use it
you want another tool to use the exact branch names from Cin7, for reports or dropdowns.
Watch out
every branch becomes its own bundle, so each following module runs once per branch and uses operations accordingly.
Cin712

List Contacts

Search

In Make“Lists all contacts.”

Brings back the contacts of your Cin7 account, one bundle each, so you can copy them to another app or check whether someone is already there.

When to use it
before Create a Contact to avoid a duplicate, or to fill a mailing list with your Cin7 customers.
Watch out
the module may return zero, one or many contacts, and each one runs the next modules once. Plan for the empty case too.
Cin713

List Payments

Search

In Make“Lists all payments.”

Pulls the payments recorded in Cin7, one bundle per payment, which makes it easy to copy them into a spreadsheet or an accounting app.

When to use it
finance wants payment data outside Cin7, or you need a payment ID before Update a Payment.
Watch out
a long list means many bundles, and each module after it counts one operation per bundle.
Cin714

List Product Categories

Search

In Make“Lists all categories of products.”

Returns every product category defined in Cin7, so your shop, catalog sheet or reporting tool can reuse the same category names.

When to use it
you build a product report or a catalog elsewhere and want it to match how Cin7 groups products.
Watch out
the module lists categories, not products. For anything beyond categories, Make an API Call is the way in.
Need help

Need help automating Cin7 with Make?

A person reads every message.

FAQ

Cin7 and Make: common questions

01Is the Cin7 Make integration free?
Yes, Cin7 is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. You still need your own Cin7 Omni subscription.
02What do you need to connect Cin7 to Make?
You need an active Cin7 Omni account and to be logged in to it. In Cin7, open Settings, go to API v1 under Integrations & API, click Add New API Connection and give it a short name. Copy the API key and the API Username that appear. In Make, add a Cin7 module, click Create a connection, paste both values and save. Naming the connection is optional. That single connection then serves all 14 Cin7 modules in every scenario you build.
03Can a Cin7 scenario start automatically when something changes in Cin7?
No, Cin7 has no trigger in Make, neither a scheduled trigger (Make checks at a regular interval) nor an instant one (the app calls Make through a webhook). You still have two ways to start. You can put a trigger from another app first, for example a new form entry, and let the Cin7 modules act after it. Or you can open a scenario with a Cin7 search such as List Payments and let the schedule run it, every 15 minutes by default, with 15 minutes as the minimum on the Free plan.
04What if the Cin7 module you need is missing in Make?
Use Make an API Call. It sends any request to the Cin7 API with the connection you already have, so you are not limited to contacts, payments, branches and product categories. You need the Cin7 API documentation to know which endpoint to call and what to send. Test the request with Run once and read the bundle it returns before you build on it. Note that the Make documentation for Cin7 is marked as AI generated, so check important details against the Cin7 documentation.
05Should you use Make or n8n for Cin7?
It depends on the tool your team already knows. Make offers 14 Cin7 modules covering contacts, payments, branches and product categories, plus Make an API Call for the rest, all driven from a visual editor where you test with Run once. Apps like Cin7 often have an n8n node as well, so check whether one exists for Cin7 and what it covers. Then look at where you already have other scenarios running, and who on the team will maintain them over time.
Same platform

Other docs you might need on this stack.

Browse all integrations