Resources · Make integration

Cin7 Core Make integrationAutomate Cin7 Core with Make.

Can Make keep Cin7 Core in step with the rest of your tools? Yes: the Cin7 Core Make integration gives you 43 modules, including 8 instant triggers, 26 actions and 9 searches. This guide is for operations teams who run sales and stock in Cin7 Core, and it walks you from the connection to a working first scenario.

Try the Cin7 Core integration on MakeSee the 43 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Cin7 Core Make integration let you automate?

The Cin7 Core Make integration links your Cin7 Core account to Make so that sales, payments, stock and contacts move between apps without copy and paste. You build a scenario, the automation itself, out of modules: small bricks that each watch, create, read or change one kind of record.

Invoices that reach accounting on their own. Start with Watch New Sale Invoice Authorized, add Get a Sale, and the approved invoice lands in your bookkeeping or reporting tool. Each record that travels from one module to the next is called a bundle.

Orders from any channel, entered once. A form, a storefront or a spreadsheet row can feed Create a Customer and Create a Sale, so nobody retypes orders into Cin7 Core. Later, Add a Sale Payment records the payment on the sale when your payment tool confirms the charge.

Stock alerts before a shelf goes empty. Watch New Stock Level Update reacts to every change in product availability, and Get a Product tells your buyers exactly which item moved.

What Make does not give you here is a detailed guide: its own documentation for Cin7 Core is marked as limited because little public information exists about the app. For anything the modules do not cover, Make an API Call reaches the Cin7 Core API with the same connection. If something breaks along the way, the Make troubleshooting page helps you read the error.

Many apps also exist as n8n nodes. If you are still choosing a platform, n8n vs Make sets out the criteria, and Make training covers the basics of the editor.

Connect

How do you connect Cin7 Core to Make?

  1. 01

    Add a Cin7 Core module

    Open a scenario, click the +, search for Cin7 Core and pick any of its modules. Make then asks for a connection, which is your Cin7 Core account linked to Make once and reused by every Cin7 Core module. Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as the company or warehouse it belongs to. Then follow what Cin7 Core asks: either authorize Make on the Cin7 Core page that opens, or paste the key Cin7 Core gives you.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read your Cin7 Core account and propose the objects it finds, so the fields fill in more easily. If the module shows an error instead, the connection is where to look first.

First scenario

Your first scenario with Cin7 Core

GoalWhen an order arrives in another app, Make creates the customer and the matching sale in Cin7 Core.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module is the app where your orders arrive first: a form, a storefront or a spreadsheet.

  2. 02

    Add Create a Customer

    Click the + on the right of the first module, search for Cin7 Core and choose Create a Customer. Create the connection, then map the buyer's details from the order into the fields.

  3. 03

    Add Create a Sale

    Add Create a Sale after it. Map the customer returned by the previous module and the order data from the first one, so the sale is tied to the right buyer.

  4. 04

    Test with Run once

    Click Run once and send one test order. Open each module's bubble to read the bundles it received, then check that the customer and the sale exist in Cin7 Core.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule; a new scenario checks every 15 minutes by default. Then switch the scenario on, and new orders flow into Cin7 Core without anyone retyping them.

Triggers

What starts a Cin7 Core scenario

8 modules start a scenario when something happens in Cin7 Core. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Cin7 Core as soon as it happens.

Cin7 Core1Watch New or Updated Customer

Watch New or Updated Customer

Instant trigger

In Make“Triggers when a new customer has been created or updated.”

This trigger starts your scenario whenever a customer record in Cin7 Core is added or edited, and hands Make that customer as a bundle. Your CRM or mailing list can then stay aligned with the inventory side without anyone copying details over.

How it fires
instant. Cin7 Core calls Make through a webhook as soon as the change happens, so there is no polling interval to wait for.
When to use it
a sales rep edits a billing address in Cin7 Core and your support tool should show the same one.
Watch out
creation and edits both fire it, so one customer can start several runs; make the next module update a record rather than create a new one.
Cin7 Core2Watch New or Updated Supplier

Watch New or Updated Supplier

Instant trigger

In Make“Triggers when a supplier has been created or updated.”

Hear about every supplier that gets added or changed in Cin7 Core. Each event reaches Make as a single bundle holding that supplier, ready to be copied to a purchasing sheet or a shared vendor directory.

How it fires
instant. Cin7 Core notifies Make with a webhook the moment the supplier is saved.
When to use it
your buyers keep vendor contacts in Airtable and need new emails or addresses there without retyping them.
Watch out
an edit to an existing supplier fires it too, so click Run once and try both a new and a modified supplier before you switch the scenario on.
Cin7 Core3Watch New Payment

Watch New Payment

Instant trigger

In Make“Triggers when a new payment has been received.”

Every payment received in Cin7 Core can now reach the rest of your stack on its own. The trigger passes the payment to Make, and the modules you add next decide where it goes: accounting, a finance channel, a thank-you email.

How it fires
instant. Cin7 Core pings Make through a webhook as soon as the payment comes in.
When to use it
finance wants a message in the team chat each time a customer settles an order.
Watch out
if the next step needs the whole order, add Get a Sale after the trigger and read in Run once what each module actually received.
Cin7 Core4Watch New Sale Credit Note Authorised

Watch New Sale Credit Note Authorised

Instant trigger

In Make“Triggers when a new sale credit note is authorized.”

Refunds and returns get a clean handoff with this trigger. Once a sale credit note is authorised in Cin7 Core, Make receives it and your scenario can tell the people or tools that need to know.

How it fires
instant. Cin7 Core sends a webhook to Make as soon as the credit note is authorised.
When to use it
customer service should see approved refunds without opening Cin7 Core, or your bookkeeping tool needs the credit recorded.
Watch out
to test it, click Run once first, then authorise a credit note on a test sale; the trigger waits for that event.
Cin7 Core5Watch New Sale Invoice Authorized

Watch New Sale Invoice Authorized

Instant trigger

In Make“Triggers when a new sale invoice has been authorized.”

The moment a sale invoice is approved in Cin7 Core, this trigger hands it to Make. That makes it the natural starting point for anything that should follow a confirmed invoice: a copy in your accounting app, a message to the customer, a task for the warehouse.

How it fires
instant. Cin7 Core calls Make by webhook as soon as the invoice is authorized.
When to use it
a finance team wants every approved invoice mirrored in another tool without exports.
Watch out
each module that runs counts as an operation, one execution on one bundle, on your Make plan.
Cin7 Core6Watch New Sale Shipment Tracking Number Changed

Watch New Sale Shipment Tracking Number Changed

Instant trigger

In Make“Triggers when a sale shipment tracking number is changed.”

Customers ask where their parcel is. This trigger lets Make answer before they do: whenever the tracking number on a sale shipment changes in Cin7 Core, your scenario receives the shipment and can pass the new number along.

How it fires
instant. Cin7 Core alerts Make through a webhook as soon as the number is changed.
When to use it
sending a shipping email, or updating the order status in your online store once the carrier number is set.
Watch out
it reacts to a change of number, so a corrected typo starts a second run; word your message so it still reads well if a customer gets it twice.
Cin7 Core7Watch New Sale Voided

Watch New Sale Voided

Instant trigger

In Make“Triggers when a new sale has been voided.”

When a sale is voided in Cin7 Core, the tools downstream often carry on as if it still existed. This trigger closes that gap: Make receives the voided sale and your scenario can cancel what was started elsewhere.

How it fires
instant. Cin7 Core tells Make through a webhook as soon as the sale is voided.
When to use it
removing a cancelled order from a fulfilment board, or alerting the account manager in charge.
Watch out
voiding and deleting are two different moves; this trigger covers voids, and no module in the list watches deletions.
Cin7 Core8Watch New Stock Level Update

Watch New Stock Level Update

Instant trigger

In Make“Triggers when a change is made to product availability.”

Stock that moves in Cin7 Core can now move everywhere else too. This trigger fires on any change to product availability and hands Make the update, so a storefront, a spreadsheet or a buyer can react while the figure is still fresh.

How it fires
instant. Cin7 Core calls Make through a webhook as soon as availability changes.
When to use it
alerting purchasing when a best seller runs low, or syncing quantities to a sales channel that Make also connects.
Watch out
availability changes with every sale and adjustment, and every module that runs is counted on your plan, so keep this scenario short.
Modules

What Cin7 Core can do in Make

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

Cin7 Core1

Add a Sale Attachment

Action

In Make“Adds attachment to a sale.”

Put a document on an existing sale in Cin7 Core, such as a signed quote, a delivery note or a customs form produced by another tool. The file lands on the sale, right where your team already looks.

When to use it
a contract is signed in your e-signature app and should sit next to the order it belongs to.
Watch out
on the Free plan Make handles files up to 5 MB, so heavy scans may need a paid plan.
Cin7 Core2

Add a Sale Pack

Action

In Make“Adds a sale pack.”

This module adds a pack to a sale from outside Cin7 Core. Your scenario can log a pack once a warehouse tool or a scanning form confirms the boxes are ready.

When to use it
packers work in a separate app and the sale in Cin7 Core should reflect their progress.
Watch out
point it at the right sale by mapping it from a trigger or from List Sales, never by typing it.
Cin7 Core3

Add a Sale Payment

Action

In Make“Adds a sale payment.”

Record a payment against a sale without logging into Cin7 Core. When money arrives through a checkout or a finance tool that Make reads, this module writes it on the matching sale so balances stay right.

When to use it
your payment processor confirms a charge and the order should show as paid.
Watch out
running the scenario twice on one charge records two payments, so test on a test sale first.
Cin7 Core4

Add a Sale Shipment

Action

In Make“Adds a shipment to sale.”

Shipping details reach the sale through this module. Once a carrier label is created elsewhere, Make adds the shipment to the Cin7 Core sale and the order history is complete.

When to use it
labels are printed in a shipping app while your team follows shipments inside Cin7 Core.
Watch out
adding a shipment and changing its tracking number are separate events; the second one has its own trigger above.
Cin7 Core5

Create a Customer

Action

In Make“Creates a customer.”

New buyers from a web form, a marketplace or your CRM become customer records in Cin7 Core, so sales can be raised against them straight away.

When to use it
as the step before Create a Sale when an order comes from someone Cin7 Core has never seen.
Watch out
each run creates one more customer; check with List Customers first if the person might already exist, or you will end up with twins.
Cin7 Core6

Create a Sale

Action

In Make“Creates a sale.”

Turn an order taken elsewhere into a sale in Cin7 Core. A storefront, a quote tool or a spreadsheet row can feed it, and the sale appears ready for invoicing and payment.

When to use it
orders come through a channel that has no direct link to Cin7 Core but does connect to Make.
Watch out
map the customer from Create a Customer or Get a Customer earlier in the scenario rather than retyping names.
Cin7 Core7

Create a Stock Adjustment

Action

In Make“Creates a stock adjustment.”

Correct stock quantities in Cin7 Core from another source. After a physical count on a tablet form, or when damaged goods are logged in a shared sheet, this module writes the adjustment for you.

When to use it
warehouse staff record breakages outside Cin7 Core and inventory must follow.
Watch out
an adjustment changes availability, which can in turn start Watch New Stock Level Update in another scenario.
Cin7 Core8

Create a Supplier

Action

In Make“Creates a supplier.”

Onboard a vendor once and let Make copy it into Cin7 Core. The module creates the supplier record from whatever form, sheet or procurement tool your buyers already fill in.

When to use it
a new vendor passes approval in your purchasing workflow and should be ready in Cin7 Core.
Watch out
every run adds a supplier, so run List Suppliers before it when in doubt.
Cin7 Core9

Delete a Sale

Action

In Make“Deletes a sale.”

Removes a sale from Cin7 Core entirely. It is handy for cleaning up test orders, or sales created by mistake through another scenario.

When to use it
after testing a new order flow, to clear the dummy sales it produced.
Watch out
a deletion cannot be undone from Make, so keep this module for test sales and map the sale from a previous module.
Cin7 Core10

Delete a Sale Attachment

Action

In Make“Deletes a sale attachment.”

Take a file off a sale when it no longer belongs there: an outdated quote, a wrong invoice copy, a duplicate upload from an earlier run.

When to use it
a new version of a document replaces the old one, so the scenario deletes the old file before Add a Sale Attachment adds the new one.
Watch out
find the right file first with List Sales Attachments; a deleted file does not come back.
Cin7 Core11

Delete a Sale Payment

Action

In Make“Deletes a sale payments.”

Cancel a payment line recorded on a sale. When a charge is reversed in your payment tool, this module stops Cin7 Core from showing money that never stayed.

When to use it
a chargeback or a failed transfer is reported after the payment was logged.
Watch out
if only part of the payment is wrong, Update a Sale Payment fixes it without losing the line.
Cin7 Core12

Delete a Stock Adjustment

Action

In Make“Deletes a stock adjustment.”

Wipe out a stock adjustment that should never have been made, for instance one written twice by a scenario that ran on the same count sheet.

When to use it
cleaning up after you test a new adjustment flow.
Watch out
when the quantity is merely off, Update a Stock Adjustment is the gentler fix, because a deletion is final.
Cin7 Core13

Find a Sale Credit Note

Action

In Make“Searches for a sale credit note by ID.”

Pull up one credit note when you already know its ID, typically handed over by a trigger or an earlier module. The scenario then has the credit note in hand for a report or a message.

When to use it
after Watch New Sale Credit Note Authorised, when a later module needs the credit note fetched on its own.
Watch out
it looks up by ID, not by customer name, so map the ID rather than typing text.
Cin7 Core14

Find a Sale Fulfilment

Action

In Make“Searches for sale fulfilments by ID.”

See where a sale stands on the warehouse side. Given the ID, this module fetches the fulfilment record so your scenario can tell a customer, a rep or a dashboard how the order is progressing.

When to use it
a customer asks about an order in your helpdesk and the answer should come from Cin7 Core.
Watch out
like Find a Sale Invoice and Find a Sale Credit Note, it searches by ID, so map that ID from a previous module.
Cin7 Core15

Find a Sale Invoice

Action

In Make“Searches for sale invoices by ID.”

Fetch the invoice side of a sale by its ID. Accounting syncs and payment reminders often need the invoice rather than the order, and this module gets it for them.

When to use it
an unpaid order needs a reminder email with the invoice details attached to the message.
Watch out
it works from an ID, so place it after a trigger or a list module that supplies one.
Cin7 Core16

Get a Customer

Action

In Make“Gets a customer.”

Read one customer record from Cin7 Core so later modules can reuse what Cin7 Core stores about that buyer without asking twice.

When to use it
a sale comes in and the email you send should greet the buyer properly.
Watch out
it targets one known customer; to browse or check for duplicates, List Customers is the right module.
Cin7 Core17

Get a Product

Action

In Make“Gets a product.”

One product, fully loaded: this module fetches a product from Cin7 Core so the scenario can reuse its data in a listing, a quote or an alert.

When to use it
a stock update arrives and the message to purchasing should say which product it is, not just a code.
Watch out
for availability figures, Find a Products Availability is built for that question.
Cin7 Core18

Get a Sale

Action

In Make“Gets a sale.”

Bring everything Cin7 Core holds on a single sale into your scenario. A flow that starts from a payment, an invoice or a voided order can add this module to work with the sale itself.

When to use it
a trigger gives you a sale reference and the next step needs the sale.
Watch out
each call is one more operation; skip it when the trigger already carries what you need, which Run once will show you.
Cin7 Core19

Get a Sale Pack

Action

In Make“Gets a sale pack.”

Check what was packed for a sale. The module retrieves a sale pack so your scenario can confirm packing before telling the carrier or the customer.

When to use it
a shipping app should only book a pickup once the pack exists in Cin7 Core.
Watch out
no trigger watches packs, so this check runs inside a scenario started by something else.
Cin7 Core20

Get a Stock Adjustment

Action

In Make“Gets a stock adjustment.”

Read back a single stock adjustment to audit it or pass its details on. It helps when a manager wants proof of what was changed before approving anything else.

When to use it
right after Create a Stock Adjustment, to log the saved result in an audit sheet.
Cin7 Core21

Get a Supplier

Action

In Make“Gets a supplier.”

Grab one supplier's record from Cin7 Core and reuse it downstream: an order request to the vendor, a contact card in your CRM, a line in a purchasing report.

When to use it
a buyer wants the vendor's details dropped into a purchase request form.
Watch out
the scenario must know which supplier; List Suppliers or Watch New or Updated Supplier can provide it.
Cin7 Core22

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the other modules does what you need, this one lets you call any endpoint of the Cin7 Core API with the connection you already set up. It is your way around a missing module.

When to use it
a record type or an operation you need is absent from the list on this page.
Watch out
you write the request yourself, and Make marks its documentation for this app as limited, so keep the Cin7 Core API reference open.
Cin7 Core23

Update a Customer

Action

In Make“Updates a customer.”

Keep customer records in Cin7 Core current from wherever they change first. A new address in your CRM or a new email from a form flows into the existing record instead of a fresh one.

When to use it
your CRM is where reps edit contacts and Cin7 Core must follow.
Watch out
Watch New or Updated Customer on the same record can bounce the change back; avoid running both directions on the same data.
Cin7 Core24

Update a Sale

Action

In Make“Updates a sale.”

Change a sale that already exists in Cin7 Core, so it matches what the customer asked for after the order was placed.

When to use it
an order amendment is approved in your helpdesk and the sale should reflect it.
Watch out
try it on a test sale with Run once and check the result in Cin7 Core before you switch the scenario on.
Cin7 Core25

Update a Sale Payment

Action

In Make“Updates a sale payment.”

Fix a payment already logged on a sale when your payment tool reports something different from what was recorded. The line stays, and its content catches up.

When to use it
a correction arrives from your payment provider after the payment was entered in Cin7 Core.
Watch out
when the payment never happened at all, Delete a Sale Payment is the honest fix.
Cin7 Core26

Update a Stock Adjustment

Action

In Make“Updates a stock adjustment,”

Correct an adjustment that went in with the wrong figures, without deleting it and starting over. The record stays; the numbers change.

When to use it
a recount shows that the first adjustment was off.
Watch out
locate it with List Stock Adjustments or Get a Stock Adjustment first, so you edit the right one.
Cin7 Core27

Find an Assembly

Search

In Make“Searches for assembly by status, sale id or other fields.”

Look up assemblies in Cin7 Core by status, by sale or by other criteria. As a search, it can return zero, one or several bundles, and each one runs through the modules that follow.

When to use it
a production lead wants the assemblies tied to a given sale listed in a shared sheet.
Watch out
an empty result simply stops that branch, so test with a sale that really has assemblies.
Cin7 Core28

Find a Products Availability

Search

In Make“Searches for a product availability.”

Ask Cin7 Core how much of a product is available. The answer can feed a storefront, a quote or a reorder alert.

When to use it
before confirming an order that came through another channel, to check stock first.
Watch out
it is a search, so it may return several bundles; plan the next modules for more than one result.
Cin7 Core29

List Customers

Search

In Make“Gets a list of customers.”

Returns your customers from Cin7 Core as a series of bundles, one per customer, for exports, clean-ups or checks before creating someone new.

When to use it
checking whether a buyer already exists before Create a Customer.
Watch out
each customer returned runs the modules after it, so a long list costs more operations than it looks.
Cin7 Core30

List Products

Search

In Make“Gets a list of products.”

Pull the product catalog out of Cin7 Core, one bundle per product, to fill a price sheet, a marketplace feed or a catalog review.

When to use it
building a product export that your sales team can read without a Cin7 Core login.
Watch out
on the Free plan a run stops after 5 minutes, which a long catalog may reach.
Cin7 Core31

List Sale Payments

Search

In Make“Gets all sale payments.”

Gather the payments recorded on sales so you can reconcile them with your bank or accounting tool. Each payment arrives as its own bundle.

When to use it
finance compares what Cin7 Core logged with what actually hit the account.
Watch out
for the single payment that just came in, Watch New Payment is lighter than listing everything again.
Cin7 Core32

List Sales

Search

In Make“Gets a list of sales.”

Bring a list of sales into your scenario, each sale as its own bundle, ready to be copied, counted or checked.

When to use it
feeding a sales dashboard in a spreadsheet, or finding the sale that a pack or a payment should attach to.
Watch out
every sale returned is one more pass through the next modules, so keep the scenario after it lean.
Cin7 Core33

List Sales Attachments

Search

In Make“Gets a list of sales attachments.”

See which files are attached to sales in Cin7 Core. The list lets a scenario archive documents to cloud storage or spot the one to remove.

When to use it
backing up signed contracts from Cin7 Core into a shared drive.
Watch out
on the Free plan, files that move through the scenario are capped at 5 MB.
Cin7 Core34

List Stock Adjustments

Search

In Make“Gets a list of stock adjustments.”

Review stock adjustments in bulk: the module lists them so a scenario can send them to an audit sheet or to a manager's inbox.

When to use it
an inventory manager wants every adjustment reviewed in one place.
Watch out
it is also how you find the adjustment to fix before Update a Stock Adjustment.
Cin7 Core35

List Suppliers

Search

In Make“Gets a list of suppliers.”

Get your supplier list out of Cin7 Core, one bundle per vendor, for a directory, a mailing or a duplicate check.

When to use it
before Create a Supplier, or to refresh the vendor tab of a purchasing sheet.
Watch out
each vendor runs the following modules once, which counts on your plan.
Need help

Need help automating Cin7 Core with Make?

A person reads every message.

FAQ

Cin7 Core and Make: common questions

01Is the Cin7 Core Make integration free?
Yes, Cin7 Core is a standard app in Make, so it works on the Free plan. That plan keeps 2 scenarios active at once, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Your Cin7 Core subscription is a separate matter that Make does not cover.
02What do you need to connect Cin7 Core to Make?
A Make account and a Cin7 Core account you can sign in to. Add any Cin7 Core module, click Create a connection, name it if you wish, then authorize Make on the Cin7 Core page or paste the key Cin7 Core provides, and click Save. Make's documentation lists no extra prerequisite, but it is marked as limited, so have admin access to Cin7 Core ready in case the app asks for it.
03Do Cin7 Core triggers fire in real time in Make?
Yes. All 8 Cin7 Core triggers are instant: Cin7 Core calls Make through a webhook as soon as the event happens, whether it is a new payment, an authorized invoice, a voided sale or a change in stock. You can spot them in the editor by the lightning badge on the module. Scenarios that start from another app instead follow their schedule, every 15 minutes by default. That lets a payment or an invoice reach your other tools while the information is still fresh.
04What if a Cin7 Core module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Cin7 Core API with the connection you already created, so you are not limited to the 43 listed modules. You will write the request yourself, and Make marks its Cin7 Core documentation as limited, so keep the app's own API reference open. For a record Cin7 Core does not handle, look for another app that does. Test the call with Run once before you rely on it.
05Should you use Make or n8n for Cin7 Core?
It depends on what your team already runs. On Make, Cin7 Core comes with 43 ready modules, including 8 instant triggers and a Make an API Call module, and scenarios are built visually. Many apps also have an n8n node, so check whether Cin7 Core has one before choosing. Pick the platform your team knows and maintains, then compare both on the modules your scenario actually needs. The n8n vs Make comparison linked higher on this page lays out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations