Cin7 Core in Agent Builder

The Cin7 Core step lets an agent read your Cin7 Core account as part of a run. It can list last week's sales, look up a product, check how many of a part are available, or find a customer. Each step does one thing, picked from 9 actions, and hands what Cin7 Core sends back to the next step. Every action reads. None of them creates a sale, changes a quantity, or raises a purchase. Cin7 Core has no trigger of its own, so something else starts the run: a schedule, or an alert from another system such as BigChange.

app.centrus.ai/app/agents/workflow-builder

Agents

Build modular AI workflows with reusable nodes

Weekly sales summary

1,240 / 10,000 creditsValidateResetRunsSettingsUpdate & Publish

Monday at 07:00

Weekly · Mon at 07:00

Last week's sales

List sales

2

Write the summary

GPT-5.6 Terra

Email accounts

1 action enabled

AI builderMap

1. 1Cin7 Core in the Integration group of the Nodes panel.
2. 2The step on the canvas. Its summary shows the action, List sales.
3. 3Connection: this agent's Cin7 Core account. The line reads Cin7 Core.
4. 4Endpoint: the action the step performs, chosen from the nine.
5. 5The action's fields. The date field is labelled ISO 8601 and holds the start of the week.

Centrus works alongside Cin7 Core. Products, stock, customers, sales and purchases stay in Cin7 Core, and the agent reads them there. It does not replace Cin7 Core. A file you send still comes from a later Excel or Outlook step. To ask about the same records in a conversation rather than in an agent, see Cin7 Core in chat. Connecting chat does not connect this step.

Open the agent in Agent Builder and find Cin7 Core in the Integration group of the Nodes panel. It sits after Fixflo and before GoHighLevel. Drag it onto the canvas and connect the step before it to its left-hand side. Until you choose an action, its summary on the canvas reads No endpoint selected.

Monday at 07:00

Weekly · Mon at 07:00

Cin7 Core

No endpoint selected

2

1. 1Cin7 Core in the Integration group. Drag it onto the canvas.
2. 2The new step. It reads No endpoint selected until you choose an action in its Details panel.

On a phone, Agent Builder shows the canvas only. The Nodes panel is hidden on screens narrower than 768 pixels and the Details panel on screens narrower than 1,024 pixels, so you can follow an agent's steps on a phone but need a tablet or computer to add a Cin7 Core step or change its settings.

09:41

Centrus

Agents

Build modular AI workflows with reusable nodes

Chase overdue invoices

Save and Publish

Monday at 07:00

Weekly · Mon at 07:00

Last week's sales

List sales

Write the summary

GPT-5.6 Terra

Email accounts

1 action enabled

The Cin7 Core connection belongs to this agent alone. It is separate from the Cin7 Core connection in chat, so connecting one does not connect the other. One connection covers every Cin7 Core step in the agent, so you only connect once per agent. The connect window says so: one key for the company, and chat connect and this node are separate.

You need two values from Cin7 Core: an Account ID and an Application Key. The connect window says they come from the Cin7 Core API page. If you cannot see that page, ask the person who administers Cin7 Core for the values. The same two values are what an administrator pastes on the Integrations card for chat, but that card and this step keep separate copies.

1. 1Save the agent with Save draft. Until it has been saved once, the Connection section reads Save this workflow as a draft first, then connect the account. and Connect is greyed out.
2. 2Select the Cin7 Core step. In the Details panel, open Connection and click Connect.
3. 3In the Connect Cin7 Core window, enter the Account ID and Application Key, then click Connect.
4. 4Centrus asks Cin7 Core who the key belongs to. If Cin7 Core accepts the two values, Connection reads Connected, followed by Cin7 Core.

Centrus checks the two values when you click Connect, by asking Cin7 Core for the company on the key. If either field is empty, nothing is saved and the window stays open with Cin7 Account ID and Application Key are required. If Cin7 Core rejects the key, nothing is saved and the message starts Could not verify Cin7 credentials. A wrong key usually continues Cin7 rejected the credentials (401). Try a dry run after a successful connect, as described under Test before it goes live.

The check also learns the company name and the currency on that Cin7 Core account. They are saved with the connection, but the Connection line does not show them. Every connected Cin7 Core step reads Connected · Cin7 Core, so the line does not tell two agents apart. The agents in Copy from existing agent are labelled the same way.

Reusing a connection. If you have already connected Cin7 Core on another agent you created, choose that agent under Copy from existing agent. Centrus fills in the two fields from it, and you click Connect to save them on this agent. The list only shows agents you created that are not archived and have a Cin7 Core connection, so an agent someone else shared with you never appears. When there are none, the box reads No other agents with this connection.

Sharing and copying the agent. When you share an agent, its Cin7 Core connection stays with it, and everyone who runs it uses that connection rather than their own. When you duplicate an agent, the steps are copied but the connection is not, so connect Cin7 Core again on the copy. Copy from existing agent makes that quick. For the details, see Share an agent.

Disconnecting. Disconnect removes the credentials from this agent only. Its Cin7 Core steps stop working until someone connects it again. Other agents keep their own connections, and the Cin7 Core connection in chat is left as it is.

Select the step and open Endpoint in the Details panel. The section's own line reads Choose the Cin7 Core action this step should run. Endpoint tool type holds all 9 actions in one list, in this order: List brands, List products, Get product, Get product attachments, Get stock, List customers, List sales, Get sale, List purchases. The list has no search box and no headings. With only nine, you can see the whole list without scrolling far. The tables at the end of this guide say what each one returns.

Keep Set endpoint fields here when the step sits in the agent's main flow and the action is one of the four lists below. Let AI populate endpoint fields hides the fields so that an AI can fill them, but on a step in the main flow nothing fills them in when the step runs. To have an AI choose the values, attach the step to an Intelligence step as a tool, as described below. That is also the only way Get stock, Get product, Get sale, Get product attachments and List brands receive the values you care about.

On a step in the main flow, Get stock, Get product, Get sale, Get product attachments and List brands do not send the values you type. The step calls Cin7 Core with empty fields. Get stock then fails with sku is required. even when SKU looks filled in. Get product fails with Pass a product id or an exact SKU. Get sale fails with id is required. Get product attachments fails because the product ID is required. Put those five on an Intelligence step as tools, so the AI supplies the SKU or the ID when it calls them. List products, List customers, List sales and List purchases do send the filters you type.

Each action then shows its own fields in a box titled with the action's name. The label on a field is the first sentence of its description, and a required field has an asterisk. That is why the three date fields on List sales are all labelled ISO 8601. The grey line under each one tells them apart: sales created after this time, sales updated after this time, and the upper bound. List purchases has the same two date labels, and no field for sales created after a time. Type the time as Cin7 Core expects it, for example 2026-10-05T00:00:00 for 00:00 on 05/10/2026.

To use a value from an earlier step, open Step data references at the top of the Details panel and click a field to copy its reference, then paste it into a text field. A text field on List sales, such as the date or the search, keeps the reference. Page number and Page size are number fields, so a reference pasted into them is turned into a number and lost. On the four lists those two fields are not used anyway: the step always starts at the first page and asks for 100 rows at a time, up to five pages.

What the step passes on. List products, List customers, List sales and List purchases pass on one item per row, so fourteen sales become fourteen items. The step's summary reads Found 14 Cin7 rows. Later steps reach each row through Step data references, and an Intelligence step reads all of the items together. Get stock passes on one item, and the locations and batches sit inside it in a list called rows. Get product and Get sale pass on one item, with found and the record. Get product attachments passes on one item holding every attachment. List brands passes on one item holding the brands, not one item per brand. The summary for those five uses an internal name, so read the output in the run rather than the summary line.

List sales is the usual weekly list. Search is a contains match across the order number, the status, the customer, the invoice number, the customer reference and the credit note number. A start time is sales created after that time, or sales updated after that time. An end time is the upper bound, not a second start time. Sale status is the status name Cin7 Core uses. With no filters the step still returns rows, up to five pages. Get sale then fetches one sale, including its lines, but only when an Intelligence step supplies the sale ID. A sale ID from the list is on each item the list passed on.

Get stock is one SKU at a time. The help line says to quote Available, and not to work it out from the other quantity fields. One SKU can come back as several rows, one for each location and batch, for example Main warehouse and a van. Optional location name narrows that. Because the main flow does not send SKU, the morning stock email and the job check both put Get stock on an Intelligence step. Get product is the same shape: pass a product ID, or an exact SKU. Cin7 Core treats a SKU as a prefix, and Centrus keeps the result only when the SKU matches, ignoring case. A prefix such as PMP-03 is not returned as PMP-03223. If nothing matches exactly, the item says it was not found.

List products sends a SKU prefix and a product name prefix. Neither is a contains match, and a brand is not a filter: the help line says the brand is ignored. It does not download the whole catalogue. List customers sends a customer name prefix, or a customer ID. A general search is ignored, and this list is not kept in a cache between runs. List purchases sends a search across the order number, the status, the supplier, the invoice number and the credit note number, plus an updated-after time, an upper bound and a status. It has no field for purchases created after a time. List brands asks Cin7 Core for the first page of brands, up to 1,000. On the main flow the optional name prefix is not sent, so the step returns that first page as one item.

Get product attachments needs the product ID from Get product, not a SKU. The help line says the query is the product ID. Each attachment comes back with its type, a download address and whether it is the default. The body is every attachment, not only images. Like Get stock, this only receives the ID when an Intelligence step calls it.

As a tool for an Intelligence step. Connect a Cin7 Core step to the Tools side of an Intelligence step and its Details panel changes. Instead of one endpoint, Actions lets you choose several, with a search box, and the AI decides when to call each one and fills in the fields itself. That is how Get stock receives a SKU. The step's summary on the canvas lists up to three actions. The notes on the four long lists tell the AI not to call them, and to use the Ingest step instead, because a wide list would be loaded into the AI. Prefer Get stock, Get product, Get sale and Get product attachments as tools, and keep List sales, List products, List customers and List purchases on the main flow.

Weekdays at 07:00

Daily at 07:00 · Mon, Tue, Wed, Thu, Fri

Write the stock note

GPT-5.6 Terra

Stock lookup

Get stock, Get product

1

1. 1The Cin7 Core step attached to the Intelligence step as a tool.
2. 2Actions: Get stock and Get product, which the AI fills in itself.
3. 3Pause for approval, left off. A morning email should not wait for a click on every SKU.

Pause for approval appears on every Cin7 Core step but only applies to calls an AI makes, so it has no effect on a step in the main flow. Every Cin7 Core action is a read, so there is nothing in Cin7 Core to undo and usually nothing to approve. Leave it off for the stock email. Turn it on only if you want someone to allow each lookup before Cin7 Core is asked. Approve or reject from the Runs panel.

Cin7 Core has no trigger of its own. Nothing in Cin7 Core, such as a sale or a low stock level, starts the agent by itself. You start the run from somewhere else and then use the Cin7 Core step. Two patterns cover most agents. A Schedule trigger runs it at a time you choose, for example 07:00 each weekday for a low-stock email, or 07:00 every Monday for a sales summary. An alert from another system, such as the BigChange webhook, runs it when a job is booked, and an Intelligence step then checks Cin7 Core for the parts on that job. Setting up a schedule is covered in Run an agent on a schedule. Setting up another system's alert is covered in Start an agent from a system alert.

Job booked

Job created

Check the parts

GPT-5.6 Terra

Stock for the job

Get stock

1. 1Connection on the BigChange webhook. This is the BigChange REST connection, not Cin7 Core. Cin7 Core has no trigger of its own.
2. 2Event types: the events that start a run. Only Job created is ticked, for a job that has just been booked.
3. 3Set this up in BigChange: the steps to follow in BigChange and the address to paste there.
4. 4Simulate webhook: runs the agent once with a sample alert. The Cin7 Core steps after it still read Cin7 Core.

What the Cin7 Core step should read from the alert. The BigChange trigger hands on data.entityId, the ID of the job that was created. The usual next step is BigChange REST Get job, with Job ID or reference set to {{ trigger.json.data.entityId }}, so the agent has the job, the site and the parts. Get stock must not sit on the main flow with a SKU typed in, or with a reference pasted in: that field is not sent, and the step fails with sku is required. Put Get stock on the Intelligence step, as in the figure, and tell that step to call it for each part on the job. The webhook uses the agent's BigChange REST connection, so this agent needs both connections. The events and what each alert contains are in BigChange REST in Agent Builder.

A schedule does not hand on a sale or a SKU. You either type the filters on a list step, as Last week's sales does with 2026-10-05T00:00:00, or you tell the Intelligence step which SKUs to ask for. There is no Cin7 Core date window called This week. You change the time in the field when you want a new window, or you leave it empty and take the first pages. A simulated BigChange alert is a real run, not a dry run: the Cin7 Core steps still read Cin7 Core, and the run uses credits. Alerts and schedules only start runs once the agent is published. Simulate webhook and Run now work on drafts.

Weekdays at 07:00

Daily at 07:00 · Mon, Tue, Wed, Thu, Fri

Write the stock note

GPT-5.6 Terra

Stock lookup

Get stock, Get product

Email the warehouse

1 action enabled

Morning stock check emails the warehouse at 07:00 each weekday if the parts you watch are short. Stock lookup is a tool on Write the stock note, with Get stock and Get product chosen. The instructions name the SKUs, for example PMP-UPS3 for the pump Meridian FM keeps for Northgate Housing, and the location Main warehouse. The AI calls Get stock for each SKU and quotes Available. It does not subtract one quantity from another. Email the warehouse sends the note from the agent's Outlook connection, to Sarah Price. Each SKU is one Cin7 Core call. Two SKUs cost two credits for that step, on top of the run, the writing and the email.

Job booked

Job created

Read the job

Get job

Check the parts

GPT-5.6 Terra

Stock for the job

Get stock

Email stores

1 action enabled

Parts on a booked job checks Cin7 Core when BigChange books a job, before anyone rings the stores. Job booked is a BigChange webhook with Job created ticked. Read the job uses Get job with {{ trigger.json.data.entityId }}, so the agent has job J-10482, the boiler service at Riverside House for Northgate Housing, and the parts on it. Check the parts has Get stock as a tool and calls it for each part, quoting Available at Main warehouse. Email stores sends Dylan Hughes, or the stores desk, only the parts that are short. A Loop around a main-flow Get stock would not pass the SKU through, so the lookup stays on the Intelligence step. The agent needs a BigChange REST connection for the webhook and Get job, and a Cin7 Core connection for the stock. Connecting one does not connect the other.

Monday at 07:00

Weekly · Mon at 07:00

Last week's sales

List sales

Write the summary

GPT-5.6 Terra

Email accounts

1 action enabled

Weekly sales summary emails accounts at 07:00 every Monday. Last week's sales uses List sales with the created-after field, labelled ISO 8601, set to 2026-10-05T00:00:00. The filters are sent, and the step passes on one item per sale, up to 500. Write the summary reads them together: who ordered, the order number such as SO-10482, the total in GBP, and anything still open. Email accounts sends it to Priya Shah. The list costs 1 credit however many sales it returns. Change the time in the field when you want the next week. There is no button for This week.

A dry run is the safe way to try a Cin7 Core step. Open Runs in the toolbar, click Run now and choose Dry run (no actions performed). Every Cin7 Core action is a read, so List sales, Get stock and the rest call Cin7 Core for real and you see real rows. There is no Cin7 Core write for a dry run to skip. Run for real performs the same reads. The difference is the other steps: a dry run skips an Outlook send, and the whole run costs 1 credit.

{
  "handles": { "main": 14 },
  "items": {
    "main": [
      {
        "OrderNumber": "SO-10482",
        "Status": "COMPLETED",
        "Customer": "Northgate Housing",
        "OrderDate": "2026-10-06T09:40:00",
        "Total": 186.4,
        "Currency": "GBP"
      }
    ]
  }
}

Open a step in the run to see its output. The panel shows the first 50 items of each output, and later steps still receive all of them. A Get stock step on the main flow fails in a dry run the same way it fails for real, with sku is required., because the SKU still is not sent. Test that lookup by running the Intelligence step that calls it. A simulated BigChange alert is not a dry run, so use Run now when you want the Outlook step held back. For Run now, dry runs and the Runs panel in full, see Test an agent before it goes live.

A Cin7 Core step costs 1 automation credit each time it runs successfully, whatever the action and however many rows it returns. A step that fails costs nothing. When the step is a tool, each call the AI makes costs 1 credit, so eight SKUs cost eight credits for Get stock. Cin7 Core has no trigger. A run started by a schedule or by the BigChange webhook still costs 1 credit for the run, like any other run, and those triggers themselves are free.

A single list is cheaper than asking for each sale on its own. List sales for the week is 1 credit. Following it with Get sale once per sale, from an Intelligence step, would be one credit per sale. For allowances, limits and how to see what each run cost, see Automation credits and usage limits.

• 500 rows on a list. List products, List customers, List sales and List purchases fetch up to five pages of 100, starting at page 1, and pass on one item per row. Page number and Page size on the step are not used. Ingest stops at the same five pages. See Large lists.
• Five actions ignore their fields on the main flow. Get stock, Get product, Get sale, Get product attachments and List brands only receive a SKU or an ID when an Intelligence step calls them. See Choose an action.
• Prefixes, not contains. On List products, SKU and name match the start of the value. A brand is ignored. On List customers, the name is a prefix and a general search is ignored. On List sales and List purchases, search is a contains match.
• Quote Available. Get stock returns one row per SKU, location and batch, inside a single item. Use the Available figure. Do not subtract the other quantities.
• Dates are year first, with a time. Type 2026-10-05T00:00:00. The fields are labelled ISO 8601. An end date is the upper bound. List purchases has no created-after field. There is no This week shortcut.
• About 8 MB per read. A single read that returns more than about 8 MB fails. The message names the action by an internal id. Narrow the filters.
• Busy periods. Cin7 Core allows about 60 calls a minute. If it says it is receiving too many, Centrus waits and tries again up to three times before the step fails. Each call is given 30 seconds.
• Per-user integration mode. The Connection section says the step still uses the agent's own connection, because Cin7 Core has no per-user credentials. In that mode the step still fails, and the message says the action is not supported and names it by an internal id. Keep agents that use Cin7 Core on the agent's own connection.
• 1,000 brands, one item. List brands asks for the first page only, with a limit of 1,000. It is not one of the wide lists, and on the main flow the name prefix is not applied.
• Exact SKU on Get product. A prefix that Cin7 Core would answer with a different product is dropped. The item says it was not found.
• Published agents only. Schedules and BigChange alerts only start runs once the agent is published. Run now and Simulate webhook work on drafts.

• Cin7 Core is not connected on this automation. Open the step's Connection section and click Connect. If you have duplicated the agent, the copy needs its own connection. A Cin7 Core connection in chat does not count, and neither does a BigChange connection on the same agent.
• Cin7 Account ID and Application Key are required. Connect refuses to save until both fields are filled in.
• Could not verify Cin7 credentials. Cin7 Core did not accept the two values. A wrong key usually continues Cin7 rejected the credentials (401). Check them on the Cin7 Core API page, then connect again. Nothing was saved.
• Stored Cin7 credentials are incomplete. The saved connection is missing the account ID or the application key. Disconnect and connect again with both.
• sku is required. Get stock was run from the main flow, so the SKU in the box was not sent. Attach the step to an Intelligence step and let the AI pass the SKU. The same shape of failure is Pass a product id or an exact SKU. on Get product, id is required. on Get sale, and a missing product ID on Get product attachments.
• No product with that exact SKU. Cin7 Core answered with a different product because the SKU is a prefix, and Centrus dropped it. Pass the full SKU, or the product ID from Get product.
• Limit must be between 1 and 100. Page size was outside that range. On the four lists the step uses 100 itself, so you can leave Page size empty.
• No action selected. The step has no action yet. The message names the step by an internal id. Choose an action under Endpoint tool type.
• An alert never starts the agent. Cin7 Core does not listen for alerts. Check the Schedule is published, or the BigChange webhook on the same agent: the event type ticked, and the webhook added in BigChange. See BigChange REST in Agent Builder.
• The step fails in per-user mode. The Connection note says Cin7 Core keeps the agent's own connection, but the run still stops. The message says the action is not supported in that mode and names it by an internal id. Switch the agent back to its own connection.
• No other agents with this connection. None of the agents you created has a Cin7 Core connection. Enter the two values by hand.
• A list stops at 500 rows. That is five pages of 100. Ingest stops at the same point. Narrow the date or the search.
• The date fields look the same. They are all labelled ISO 8601. Read the grey line under each one before you type the time.

The Cin7 Core step offers 9 actions. All 9 read from Cin7 Core, and none of them change it. Every endpoint below is on https://inventory.dearsystems.com/ExternalApi/v2. Connect also calls GET /me to check the key. That call is not one of the nine actions.