Resources · Zapier integration

Cin7 Core Inventory Zapier integrationAutomate Cin7 Core Inventory with Zapier.

The Cin7 Core Inventory Zapier integration gives you 15 triggers, 15 actions and 10 searches. Every trigger is instant, the app works on the free plan, and this page shows what each Zap costs and where it tends to break.

See the 40 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Cin7 Core Inventory Zapier integration actually does

It links your Cin7 Core account to Zapier, the tool that runs automations between apps. Something happens in Cin7 Core (a sale, a payment, a stock change), and Zapier carries out the next steps for you, in Cin7 Core itself or in another tool you already use. You set it up once, and it runs on its own.

Three results come back again and again. First, an order desk that fills itself: an order captured somewhere else becomes a sale in Cin7 Core through Create Sale, then gets its pack and its shipment through Add Sale Pack and Add Sale Shipment. Second, cash that is logged where it belongs: a payment taken elsewhere lands on the right sale with Add Sale Payment, once Find a Sale Extended has located the order. Third, stock alerts that leave the warehouse: Stock Level Update starts a Zap the moment availability moves, so a buyer hears about a low line without opening the back office.

What it does not do matters just as much. There is no delete action at all: a Zap can create and update, never remove. Purchases only work one way: a Zap can react to New Purchase / Updated Purchase, but no action creates or edits a purchase order. Everything the ready-made actions leave out goes through API Request (Beta), which is a tool for people comfortable with raw requests, not a shortcut.

If you are weighing other platforms, the Cin7 Core Inventory Make integration page covers the same app on Make, and the n8n vs Zapier comparison is the next read.

Vocabulary

Zapier vocabulary in one minute

Eight words, and you can read any Zap. Each one is explained here once, then used plainly on the rest of the page.

Zap
The automation you build: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap finishes successfully, and your plan counts those.
Instant vs polling
An instant trigger is reported by the app itself the moment it happens. A polling trigger is checked by Zapier on a timer set by your plan.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what was found.
Connection
Your Cin7 Core account linked to Zapier once, then reused by every step of every Zap that touches the app.
Cost

What a Cin7 Core Zap really costs

Zapier bills tasks, not Zaps. The trigger is free, and so is waiting for it.

  • TriggerNever costs a task
  • Successful actionOne task each
  • Failed actionNot counted
  • Free plan100 tasks a month, two-step Zaps only
  • App accessAvailable on the free plan

Each action that goes through counts as one task, so a Zap with three actions uses three times what a one-action Zap uses. An action that fails is not counted. Cin7 Core Inventory is not reserved for paid plans, so the free plan can run it, with 100 tasks a month. The catch: on the free plan a Zap stops at two steps, one trigger and one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below only matters for polling triggers, and every Cin7 Core trigger is instant.

Connect

Connect Cin7 Core Inventory to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Before that, make sure you have a Cin7 Core account, plus read or write access to anything you do not own and want the Zap to touch.

  2. 02

    Pick Cin7 Core Inventory

    Type the app name in the search box of the dialog, select Cin7 Core Inventory, then click Add connection. A new tab opens on the Cin7 Core side so you can sign in with your own account.

  3. 03

    Grant access

    Sign in to Cin7 Core in that tab and allow Zapier to reach the account. From then on, every Zap step that uses Cin7 Core can reuse this connection, so you only do this once per account.

First Zap

Your first Zap: pack every new wholesale sale

GoalWhen a sale is created in Cin7 Core, keep only the ones that match your condition, then add the pack to that sale.

  1. 01

    Build: set the trigger

    Start a new Zap, choose Cin7 Core Inventory as the app and New Sale as the event. Pick your connection. The editor shows a lightning bolt, the sign of an instant trigger.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent sales of the account, so you map fields on a real order instead of guessing what the data will look like.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field to look at, the rule and the value. Pick a text rule for text and a number rule for numbers, or the filter never passes.

  4. 04

    Add Sale Pack

    Add Cin7 Core Inventory again, event Add Sale Pack. Map the Sale ID from the trigger, then fill status, SKU, location and quantity, all five required.

  5. 05

    Test, then Publish

    Test the action and read what came back in Cin7 Core. Then click Publish. The filter makes this a multi-step Zap, so it needs a paid plan.

Triggers

Cin7 Core Inventory triggers

15 events start a Zap when something happens in Cin7 Core Inventory, and 15 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Customer / Updated Customer

Instant trigger

In Zapier“Triggered when customers are created or updated.”

One event watches your customer list both ways: it starts the Zap when a customer is added in Cin7 Core and again whenever that record is edited later.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a wholesale distributor who wants every new trade account, and every change to its terms, copied into the CRM the sales reps live in.
Watch out
the trigger asks for a Status during setup, so have that value ready before you test; an Update Customer step in the same Zap will set it off again.
2

New Product / Updated Product

Instant trigger

In Zapier“Triggered when products are created or updated.”

Your catalogue becomes a starting point: a product created in Cin7 Core starts the Zap, and so does any later edit to that product.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a merchandiser who adds lines in Cin7 Core and wants the product sheet in the team's shared spreadsheet refreshed without retyping names and SKUs.
Watch out
Status is required here too. Pair this trigger with Update Product carefully, because writing back to the product counts as an update and restarts the Zap.
3

New Purchase / Updated Purchase

Instant trigger

In Zapier“Triggered when purchases are created or updated.”

Purchase orders get their own trigger: the Zap starts as soon as a purchase is raised in Cin7 Core, and again each time someone edits it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an operations lead who wants finance told about every supplier order the moment buying commits to it, instead of finding out at month end.
Watch out
this is the only purchase operation in the integration. You can react to purchases, but no action creates or changes one, so the work stays one way.
4

Sale Additional Info Added

Instant trigger

In Zapier“Triggers when an additional information is added to a sale”

Fires on a narrow event: someone adds additional information to an existing sale in Cin7 Core. The sale itself is not new, only the extra details are.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a store that records gift-wrap or delivery notes as extra info on the sale and wants the packing team warned the moment such a note appears.
Watch out
the Zap only sees info added after it is published, so sales that already carry notes stay invisible to it.
5

Sale Attachment Added

Instant trigger

In Zapier“Triggers when an attachment is added to a sale”

Reacts when a file is attached to a sale in Cin7 Core, whether a signed quote, a proof of delivery or anything else your team uploads to the order.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an account manager who wants each purchase order sent by a big buyer filed in the shared drive the day it lands on the sale.
Watch out
if the same Zap also runs Add Sale Attachment. on that sale, the new file sets the trigger off again and the loop eats tasks fast.
6

Sale Voided/Undone

Instant trigger

In Zapier“Triggers when a sale is voided or undone.”

Covers the sales that go backwards: the Zap starts when a sale in Cin7 Core is voided or undone, which is often the step people forget to automate.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a customer service team that needs to know straight away when an order is cancelled, so nobody ships a parcel that no longer has a buyer.
Watch out
an Event Type is required during setup. Have that value ready before you test the trigger.
7

New Sale

Instant trigger

In Zapier“Triggers when a new sale is created.”

The plainest event of the lot: a sale is created in Cin7 Core and the Zap starts. It is the natural first card for anything that follows an order.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a B2B seller who wants each fresh order posted to the warehouse channel and logged in a sales tracker, with no one copying order numbers by hand.
Watch out
a Create Sale step in a Zap started by New Sale creates a loop. Keep the two in separate Zaps watching different sources.
8

Sale Credit Note Authorised

Instant trigger

In Zapier“Triggers when a sales credit note authorised.”

Waits for a credit note on a sale to be authorised in Cin7 Core. Nothing earlier in the credit note's life starts the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a finance assistant who wants every approved refund noted in the team's tracking sheet, so the refund queue and the books stay in step.
Watch out
to pull the full credit note into a later step, add Find a Sale Credit Note, which asks for a Task ID that an earlier step has to supply.
9

Sale Fulfilment Update

Instant trigger

In Zapier“Triggers when a sale's fulfilment status is updated.”

Follows the warehouse side of a sale: the Zap starts whenever the fulfilment status of a sale changes in Cin7 Core.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a dispatch supervisor who wants the account manager pinged when an order moves through picking and packing, rather than chasing the warehouse for updates.
Watch out
Event Type is required. Set it before you test, then add a filter if only some updates matter to you.
10

Sale Invoice Authorised

Instant trigger

In Zapier“Triggers when a sales invoice authorised.”

Kicks off the Zap the moment a sales invoice is authorised in Cin7 Core, which is usually the point where an order turns into money owed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a bookkeeper who wants each approved invoice copied to the accounts team's tracker, so collections can start without waiting for an export.
Watch out
for the invoice details, chain Find a Sale Invoice, which asks for a Task ID from an earlier step.
11

New Payment

Instant trigger

In Zapier“Triggers when a payment is added to a sale.”

Listens for money coming in: the Zap starts when a payment is added to a sale in Cin7 Core.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a small wholesaler whose owner wants a short message for every payment received on a large order, so credit holds can be lifted on the spot.
Watch out
Event Type is required here. And if the Zap itself runs Add Sale Payment, each payment it writes starts the trigger again, so keep those flows apart.
12

Sale Shipment Tracking Number Changed

Instant trigger

In Zapier“Triggers when a sale's shipment tracking number changed.”

Fires when the tracking number on a sale's shipment changes in Cin7 Core.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an online store that wants each buyer to receive their tracking number by email as soon as the warehouse records it, instead of answering "where is the parcel" tickets.
Watch out
a correction to a wrong number starts the Zap too, so the buyer may get a second message. Word the email so it still reads well.
13

Sale Status Change

Instant trigger

In Zapier“Triggers when a sales status is changed.”

A wide net over the order lifecycle: the Zap starts whenever the status of a sale changes in Cin7 Core.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sales manager who wants a live board of every order and its stage, updated without anyone touching it.
Watch out
the Event Type field is required, and a sale can change status several times. Add a filter if one action per status change is more than you want to pay for.
14

Stock Level Update

Instant trigger

In Zapier“Triggered when a change is made to product availability.”

Watches availability rather than documents: the Zap starts whenever a change is made to how much of a product is available in Cin7 Core.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a buyer who wants a message when a fast seller drops, paired with a filter so only the readings that meet the condition get through.
Watch out
a stock count or bulk import changes many lines at once. That sudden batch can be held back by Zapier's flood protection, and each run that gets through still costs its actions.
15

New Supplier / Updated Supplier

Instant trigger

In Zapier“Triggered when suppliers are created or updated.”

Mirrors the customer trigger on the buying side: a supplier added in Cin7 Core starts the Zap, and so does any later edit to that supplier.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a procurement team that keeps a vendor directory in another tool and wants it in step with Cin7 Core without double entry.
Watch out
Status is required at setup. And an Update Supplier step on the same supplier restarts this Zap, so keep write-backs out of it.
Actions

Cin7 Core Inventory actions

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

1

Add Sale Attachment.

Action

In Zapier“Adds attachment to sale.”

Puts a file on a sale in Cin7 Core, so the paperwork sits next to the order it concerns.

When to use it
a signed delivery note or customer purchase order that arrives by email and should be filed on the sale.
Watch out
the file name must include its extension (Picture_001.jpg, not Picture_001), and the Sale ID is required.
2

Create Customer

Action

In Zapier“Creates a new customer.”

Adds a customer record to Cin7 Core, ready for sales to be raised against it.

When to use it
a trade account form on your site that should open the account in Cin7 Core as soon as it is approved.
Watch out
name, currency, payment term, tax rule, receivable account and revenue account are all required, so those settings must exist in Cin7 Core first.
3

Add Sale Pack

Action

In Zapier“Adds pack to sale.”

Adds a pack to a sale, telling Cin7 Core which product leaves which location and in what quantity.

When to use it
picking confirmed in a warehouse app that should be reflected on the sale without a second entry.
Watch out
Sale ID, status, SKU, location and quantity are all required, and the location is the one the product is picked from.
4

Add Sale Payment

Action

In Zapier“Adds payment to sale.”

Records a payment against an existing sale in Cin7 Core.

When to use it
payments collected in a separate checkout or bank tool that should mark the matching sale as paid.
Watch out
besides the Sale ID and amount, it wants the date paid, the bank account code and a currency rate, all of them required.
5

Create Product

Action

In Zapier“Creates a new product.”

Adds a product to the Cin7 Core catalogue from data that arrives in an earlier step.

When to use it
new lines approved in a product planning sheet that should appear in Cin7 Core without retyping.
Watch out
SKU, name, category, type, costing method, unit of measure and Price Tier 1 are all mandatory; a sheet missing one of them breaks the run.
6

Create Sale

Action

In Zapier“Creates a new sale.”

Raises a new sale in Cin7 Core, with its customer and its lines.

When to use it
orders taken outside Cin7 Core, from a form or a marketplace export, that need to land in the order book as real sales.
Watch out
customer, SKU, quantity, price, tax, total and tax rule are required. If the shipping address does not match the customer's, Cin7 Core may add a new address to that customer.
7

Add Sale Shipment

Action

In Zapier“Adds shipment to sale.”

Logs a shipment on a sale in Cin7 Core, the step that closes the loop between order and delivery.

When to use it
a carrier booking made in another tool that should be recorded on the sale it belongs to.
Watch out
Sale ID, status, shipment date and package number are required. The address rule is the same as on Create Sale: a non-matching address may be added to the customer.
8

Create Stock Adjustment

Action

In Zapier“Creates a stock adjustment.”

Changes the quantity on hand for a product at one location, as a dated adjustment in Cin7 Core.

When to use it
a count done with a scanning app whose results should correct Cin7 Core directly.
Watch out
the quantity is the new on-hand figure, not a difference to add. Effective date, SKU, unit cost and location are required as well.
9

Create Stock Transfer

Action

In Zapier“Creates a stock transfer.”

Moves stock from one location to another inside Cin7 Core, as a transfer with its own dates.

When to use it
a restock request from a shop that should become a transfer from the main warehouse.
Watch out
both locations go in by name, and the departure date is required when the status is IN TRANSIT, next to the completion date, SKU and quantity.
10

Create Supplier

Action

In Zapier“Creates a new supplier.”

Opens a new supplier in Cin7 Core so purchases can be placed with it.

When to use it
a vendor onboarding form that should end with the supplier ready in Cin7 Core, not in someone's inbox.
Watch out
currency, payment term, tax rule and payable account are required alongside the name; a missing ledger account stops the step.
11

Update Customer

Action

In Zapier“Updates a customer.”

Edits an existing customer in Cin7 Core, for instance to put an account on credit hold.

When to use it
an overdue flag raised in your accounting tool that should freeze the customer in Cin7 Core too.
Watch out
only the customer ID is required, so place Find a Customer before this step to get it from a name.
12

Update Product

Action

In Zapier“Updates the product.”

Rewrites a product record in Cin7 Core from fresher data held elsewhere.

When to use it
a price or category change made in a product sheet that should flow into the catalogue.
Watch out
the product ID plus every field Create Product needs are required, so map them all, or the step fails on what you left empty.
13

Update Sale

Action

In Zapier“Updates a sale.”

Edits a sale already in Cin7 Core, keeping it in step with changes made upstream.

When to use it
a customer who changes the delivery address after ordering, through a form your team already uses.
Watch out
Sale ID and customer are required. Prices are treated as tax exclusive unless you switch Tax Inclusive on.
14

Update Supplier

Action

In Zapier“Updates a supplier.”

Changes a supplier already in Cin7 Core, from its payment term to its tax rule.

When to use it
new payment terms agreed with a vendor and recorded elsewhere, which should reach Cin7 Core without a second edit.
Watch out
unlike Update Customer, it requires the full set again: ID, name, currency, payment term, tax rule and payable account.
15

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

Sends a raw request to Cin7 Core using your existing connection, for anything the fourteen ready-made actions do not cover.

When to use it
a need that no standard action handles, if someone on the team reads API documentation comfortably.
Watch out
requests only go to domains tied to Cin7 Core. Set Stop on error to Yes if a failed call should halt the Zap.
Searches

Cin7 Core Inventory searches

10 search steps look for data that already exists in Cin7 Core Inventory, so a later step can use it.

Searches sit at the bottom of the Action event list, under SEARCH. Some action fields also offer + Add search step, which inserts the lookup just before the step and wires the result in. Three settings decide what happens when the lookup does not go as planned.

1

Find an Assembly

Search

In Zapier“Search for assembly by status, sale id or other fields.”

Looks up an assembly in Cin7 Core by status, sale id or other fields, so a later step can work with it. Whether it expects an exact value or a close one is decided by Cin7 Core, not by Zapier.

When to use it
a kitting business that needs the assembly linked to a sale before telling the workshop what to build.
2

Find a Customer

SearchFind or create

In Zapier“Search for customer by name.”

Finds a Cin7 Core customer by name and passes its record on to the steps that follow.

When to use it
before Create Sale or Update Customer, to turn a name from a form into the right account.
Watch out
the editor also shows Create DEAR customer if it doesn't exist yet? That is this same search with the box ticked, creating the customer when no match exists.
3

Find a Sale Payments

Search

In Zapier“Search for sale payments by sale id, order number, invoice number, credit note number.”

Retrieves the payments recorded on a sale, looked up by sale id, order number, invoice number or credit note number. Several payments can come back for one sale, and by default the step keeps only the first.

When to use it
a check before Add Sale Payment, so a payment already logged is not entered a second time.
4

Find a Products Availability

Search

In Zapier“Search for products availability.”

Returns availability figures for products in Cin7 Core, page by page.

When to use it
a stock answer pulled into a reply to a reseller who asks what can ship.
Watch out
page number, limit per page and Non Zero Products Only are all required, so one search only reads one page of results.
5

Find a Product

Search

In Zapier“Search for product by name or sku.”

Finds a product by its name or SKU and hands its record to the next steps. A name can match more than one product, and the default keeps the first one, so the SKU is the safer key.

When to use it
getting the product ID that Update Product requires, starting from the SKU a supplier sends.
6

Find a Sale Credit Note

Search

In Zapier“Search for sale credit note by id.”

Pulls a specific credit note on a sale, identified by its id. It is the natural follow-up when the trigger alone does not carry enough.

When to use it
after Sale Credit Note Authorised, to carry the full credit note into an accounting step.
Watch out
it requires a Task ID, which has to come from an earlier step.
7

Find a Sale Fulfilment

Search

In Zapier“Search for sale fulfilment by id.”

Fetches one fulfilment of a sale by its id. Use it when a message needs more than the trigger brought.

When to use it
after Sale Fulfilment Update, when the message to the customer needs more than the trigger brought.
Watch out
the Task ID is required here as well.
8

Find a Sale Invoice

Search

In Zapier“Search for sale invoice by id.”

Reads a sales invoice from Cin7 Core by its id, so the amounts can travel to another tool.

When to use it
chained after Sale Invoice Authorised to fill a collections tracker with real invoice data.
Watch out
the Task ID is required, mapped from the step before.
9

Find a Sale

Search

In Zapier“Search for sale by id.”

Retrieves a single sale when you already hold its Sale ID, which is required. If nothing matches, the Zap stops at this step unless you switch on the setting described above.

When to use it
a Zap started elsewhere that carries the Sale ID and needs the full order before acting on it.
10

Find a Sale Extended

Search

In Zapier“Search for sale by order number, status, customer, invoice number, customer reference, credit note number.”

The broader sale lookup: by order number, status, customer, invoice number, customer reference or credit note number. Several sales can share a status or a customer, so pick carefully what happens when more than one matches.

When to use it
a payment notice that only quotes the order number, and needs the matching sale before Add Sale Payment.

The three settings every search exposes

  1. Successful if no search results are found?
    Left at its default, a search that finds nothing stops the Zap and the dependent steps are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them to the next steps.
When it breaks

When a Cin7 Core Zap breaks

Zapier attaches no help article to Cin7 Core Inventory, and no app-specific limit is documented. What breaks is what breaks on any Zap, with a few twists that this app makes more likely.

Most of these come from the design of the integration itself: every trigger is instant and many of them cover both new and updated records. That makes loops easy to build and bulk changes easy to trigger. When a Zap misbehaves, the Zapier troubleshooting page is the place to start.

  • The past is never picked up

    A Zap only reacts to what happens after you switch it on. Sales, customers or stock moves that existed before are not processed; moving that backlog is a separate job.

  • A Zap that sets itself off

    New Product / Updated Product plus Update Product on the same item restarts the Zap after each write. The loop repeats and burns through your task count fast.

  • Bulk changes get held back

    A stock count or catalogue import can fire a huge batch of trigger events at once. Zapier's flood protection may hold that batch back instead of running it.

  • A filter that never passes

    Filter rules are typed. A text rule on a quantity, or a number rule on a status, never matches, so every run stops at the filter without a word.
Need help

Need help automating Cin7 Core Inventory with Zapier?

A person reads every message.

FAQ

Cin7 Core Inventory and Zapier: frequent questions

01Is the Cin7 Core Inventory Zapier integration free?
Yes, it works on the free plan, because Zapier does not reserve Cin7 Core Inventory for paid plans. The free plan gives you 100 tasks a month and an unlimited number of Zaps. The limit is the shape of the Zap: one trigger and one action, nothing more. As soon as a Zap needs a filter, a search step or a second action, it becomes multi-step and needs a paid plan. Plenty of useful Cin7 Core flows fit in two steps, such as a new sale logged in another tool.
02How many tasks does a Cin7 Core Zap use?
One task per action that completes successfully, and nothing for the trigger. A Zap that reacts to New Sale and runs Add Sale Pack uses one task per sale. Add Add Sale Shipment behind it and each sale costs two. An action that fails is not counted against your plan. Waiting for an event costs nothing either. Watch the triggers that cover both new and updated records, because every edit to a customer or a product starts the Zap again and each run spends its tasks.
03Does Cin7 Core Inventory trigger Zaps in real time?
Yes. All fifteen Cin7 Core triggers are instant: the app notifies Zapier the moment the event happens, so the Zap starts right away. The polling interval tied to each plan, 15 minutes on Free and 2 minutes on Professional, does not apply to any of them. That is a real advantage on the free plan, where polling apps wait for the next check. In the editor, a Zap built on one of these triggers shows a lightning bolt.
04What is needed to connect Cin7 Core to Zapier?
A Cin7 Core account, plus read or write access to anything you do not own and want the Zap to touch. The connection itself takes three moves: open Apps in Zapier, click + Add connection and pick Cin7 Core Inventory, then sign in and grant access in the tab that opens. Before building, check that payment terms, tax rules and ledger accounts exist in Cin7 Core, since several create actions require them.
05Why does a Cin7 Core Zap keep running on its own?
Usually because it writes into what it is watching. Several triggers cover both new and updated records, such as New Product / Updated Product or New Supplier / Updated Supplier. If the same Zap then runs Update Product or Update Supplier on that record, the edit counts as an update and starts the Zap again. The loop repeats and burns tasks fast. Split the flow into two Zaps, or add a filter that stops the second pass.
06What if the Cin7 Core action that is needed does not exist?
API Request (Beta) is the fallback. It sends a raw request through your existing Cin7 Core connection, so you can reach things the standard actions skip. It only accepts domains tied to Cin7 Core, and a Stop on error setting decides whether a failed call halts the Zap. It assumes someone on the team can read API documentation comfortably and test each call before relying on it. If nobody can, it is safer to hand that Zap to a specialist than to guess at the request.
07Zapier, Make or n8n for Cin7 Core Inventory?
It depends on three criteria rather than a winner. On Zapier, every Cin7 Core trigger is instant and the app runs on the free plan, which covers many two-step flows. The Zapier side also has clear edges: 15 actions with no delete, and purchases you can react to but not create or edit. If one of those gaps blocks your flow, that settles part of the question. Make has its own Cin7 Core integration page, so the operations can be compared line by line. Check each platform against your volume and your team's comfort with technical tools.
Same platform

Other docs you might need on this stack.

Browse all integrations