Cin7 Core

The Cin7 Core app connects Cin7 Core (formerly DEAR Inventory) to Sprigr Team. Agents can read and write products and product families, customers and suppliers, sales from quote through fulfilment, invoice and payment, purchases, stock adjustments, stocktakes and transfers, production orders and runs, journals and money transactions, and CRM records, with the same coverage as the Cin7 Core External API. An optional sync mirrors key records into a searchable index, and Cin7 webhooks can turn sales, purchase, product and stock changes into events.

Note

Cin7 Core ships as a marketplace app with install-wide API-key authentication. There is no OAuth: an admin enters the Cin7 Core Account ID and Application Key at install time, and every agent with the app uses that credential.

Prerequisites

• A Cin7 Core account with API access. In Cin7 Core, open Integrations & API > API v2 to find the Account ID and create an Application Key.
• Admin or Owner role in your Sprigr Team organisation to install the app.

Installing and connecting

1. Install the app and enter the credentials

   Sign in to team.sprigr.com, open Apps in the sidebar, find Cin7 Core under Available, and click Install. The app asks for two required secrets, CIN7_CORE_ACCOUNT_ID and CIN7_CORE_APPLICATION_KEY, before it will install. Both are stored encrypted. See Installing Apps.

2. Optional secrets

   CIN7_WEBHOOK_TOKEN is a bearer token you can set so the app only accepts webhook deliveries that carry it; register your Cin7 webhooks with bearer authorisation and the same value. Leave it blank if you are not using webhooks.

3. Turn on sync if you want fast lookups

   Ask your agent to enable Cin7 sync. It runs the configure_sync action with enabled: true. Until then the sync tools are no-ops and every lookup goes live to Cin7.

4. Check the connection

   The app’s settings page shows whether credentials are configured. Ask your agent “How many units of SKU ABC-123 are available?” to confirm calls succeed.

Try asking your agent

“What stock do we have on hand for the Widget Pro across all locations?”

“Create a sales order for Acme Pty Ltd: 20 units of ABC-123 at list price, ship to their default address.”

“Which purchase orders are still waiting on the supplier?”

Sync, webhooks and confirmation

• Optional searchable mirror. When sync is enabled, a backfill imports products, customers, suppliers, sales, purchases and stock availability into a private search index, and an incremental sync every 15 minutes pulls records changed since the last run using Cin7’s modified-since filters. The mirror is for resolving names to ids; the agent reads the live record before acting. Sync is throttled to stay inside Cin7’s 60-calls-a-minute limit.
• Webhooks and events. Deliveries to the app’s webhook receiver are verified, de-duplicated and emitted as cin7.sale.created, cin7.sale.order_authorised, cin7.sale.full_payment_received, cin7.purchase.order_authorised, cin7.product.updated and cin7.stock.level_changed events for workflows.
• Confirmation before destructive changes. Fifty actions, every delete and void across sales, purchases, stock, production and financials, pause for your confirmation in the chat before they run, and are marked irreversible.

What agents can do

The app exposes a single cin7_core tool that takes an action, with 298 actions at parity with the Cin7 Core External API. At a category level:

• Reference and master data: accounts, tax rules, payment terms, locations, price tiers, attribute sets, carriers, units of measure.
• Products: products, families, availability, suppliers and pricing, BOMs, attachments.
• Customers and suppliers: read, create and update, addresses and contacts, credit limits.
• Sales: the composite sale plus quote, order, fulfilment (pick, pack, ship), invoice, credit note, payment and attachments; advanced sales.
• Purchases: composite purchase plus order, stock received, invoice, credit note, payment and attachments; advanced purchases with putaways and manual journals.
• Stock: adjustments, stocktakes, transfers, write-offs, availability, movements.
• Production: production orders, runs and operations, work centres, disassembly, finished goods.
• Financials: journals, money transactions, bank transfers, chart of accounts.
• CRM: leads, opportunities and deals.
• Webhooks: list, create and delete Cin7 webhook subscriptions.

Ask the agent what it can do with Cin7 Core, or call the tool with no action, to see the full catalogue.

Common use cases

• Stock questions from sales. “Can we ship 40 of X this week?” checks availability by location and open purchase orders.
• Order entry. The agent creates a sale from a customer’s email, ready for authorisation.
• Purchasing follow-up. The agent lists purchase orders past their expected date and drafts supplier chasers.
• Production visibility. “What is on the floor today?” lists open production runs and their operations.
• Stock alerts. A workflow on cin7.stock.level_changed notifies the team when a key SKU drops below a threshold.

Troubleshooting

Not connected or credential errors The Account ID or Application Key is missing or wrong. Update the app’s secrets from the Apps page. Application Keys are created and revoked in Cin7 Core under Integrations & API.

Search finds nothing Sync is off. Ask the agent to enable Cin7 sync; the first backfill can take a while for a large account, and the settings page records the outcome.

Rate limit errors Cin7 Core allows 60 API calls a minute per account. The sync throttles itself; a burst of live lookups on top can hit the ceiling. Ask the agent to narrow the query or wait a minute.

Webhook deliveries rejected If CIN7_WEBHOOK_TOKEN is set, the Cin7 webhook must be registered with bearer authorisation and the identical token.

An action is waiting for confirmation Deletes and voids pause until you confirm in the chat.

Next steps

• Integrations Overview: See all available integrations.
• Workflows: React to Cin7 sale, purchase and stock events.
• Starshipit: Pair with Starshipit for the dispatch side of fulfilment.