Cin7 Core MCP integration for AI agents.
Connect AI agents to Cin7 Core through 5 structured actions, including get current account, get customer, and get product. Review authentication, inputs, wor…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Cin7 Core integration exposes
The Cin7 Core Agent App exposes 5 provider-backed actions for data and finance work. Its current contract lets an authorized agent retrieve the cin7 core company and account settings for the connected account, retrieve one cin7 core customer by customer id, and retrieve one cin7 core product by product id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Cin7 Core account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Cin7 Core capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_accountREADRetrieve the Cin7 Core company and account settings for the connected account.
get_customerREADRetrieve one Cin7 Core customer by customer ID.
INPUTS: id
get_productREADRetrieve one Cin7 Core product by product ID.
INPUTS: id
list_customersREADList Cin7 Core customers with optional official filters and page pagination.
INPUTS: page / limit / id / name / contactFilter
list_productsREADList Cin7 Core products with optional official filters and page pagination.
INPUTS: page / limit / id / name / sku
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
idREQUIRED- The Cin7 Core customer ID to retrieve.
get_product
idREQUIRED- The Cin7 Core product ID to retrieve.
list_customers
pageOPTIONAL- The one-indexed Cin7 Core page number to return.
limitOPTIONAL- The number of records to return. Cin7 Core allows 1 to 1000.
idOPTIONAL- Only return the customer with this Cin7 Core customer ID.
nameOPTIONAL- Only return customers whose name starts with this value.
contactFilterOPTIONAL- Only return customers with contacts matching this Cin7 Core contact filter.
list_products
pageOPTIONAL- The one-indexed Cin7 Core page number to return.
limitOPTIONAL- The number of records to return. Cin7 Core allows 1 to 1000.
idOPTIONAL- Only return the product with this Cin7 Core product ID.
nameOPTIONAL- Only return products whose name contains this value.
skuOPTIONAL- Only return products whose SKU contains this value.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current Account
Retrieve the Cin7 Core company and account settings for the connected account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_accountVerify with Get Customer
Retrieve one Cin7 Core customer by customer ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_customerSAFETY BOUNDARY
Operate Cin7 Core with explicit limits
- Authorize Cin7 Core with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Cin7 Core data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Cin7 Core rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Cin7 Core task completed successfully.
CONNECTION MODEL
API key
Cin7 Core API Application Key sent with the api-auth-applicationkey header. Create or view it with the Account ID on the Cin7 Core ExternalAPI setup page after signing in: https://inventory.dearsystems.com/ExternalAPI.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Cin7 Core.