Integration
Connect Cin7 Core Inventory to Stedi
When New Customer / Updated Customer fires in Cin7 Core Inventory, your agent runs Add event destination in Stedi. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cin7 Core Inventory and Stedi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Cin7 Core Inventory can start in Stedi
When New Customer / Updated Customer in Cin7 Core Inventory
then Add event destination in Stedi
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Cin7 Core Inventory and Stedi
Triggers and actions 13 triggers · 33 actions
- New Customer / Updated Customer
Triggers when a customer is created or updated in Cin7 Core.
- New Payment
Triggers when a payment is added to a sale (its paid amount changes).
- New Product / Updated Product
Triggers when a product is created or updated in Cin7 Core.
- New Purchase / Updated Purchase
Triggers when a purchase is created or updated in Cin7 Core.
- New Sale
Triggers when a new sale is created in Cin7 Core.
- New Supplier / Updated Supplier
Triggers when a supplier is created or updated in Cin7 Core.
- Sale Credit Note Authorised
Triggers when a sale credit note is authorised.
- Sale Fulfilment Update
Triggers when a sale's pick, pack or ship status changes.
- Sale Invoice Authorised
Triggers when a sale becomes fully invoiced.
- Sale Shipment Tracking Number Changed
Triggers when a sale's shipment tracking numbers change.
- Sale Status Change
Triggers when a sale's status changes in Cin7 Core.
- Sale Voided/Undone
Triggers when a sale is voided.
- Stock Level Update
Triggers when a product's stock level at a location changes.
- Add Sale Attachment
Attaches a file to a sale.
- Add Sale Pack
Records packing for a sale fulfilment.
- Add Sale Payment
Records a payment or refund against a sale invoice.
- Add Sale Shipment
Records shipment of a sale fulfilment, with carrier and tracking numbers.
- Create Customer
Creates a new customer in Cin7 Core.
- Create Product
Creates a new product in Cin7 Core.
- Create Sale
Creates a new sale (quote or order header) in Cin7 Core.
- Create Stock Adjustment
Creates a stock adjustment that changes on-hand quantities.
- Create Stock Transfer
Creates a stock transfer between two locations.
- Create Supplier
Creates a new supplier in Cin7 Core.
- Find a Customer
Finds customers by name, ID or contact.
- Find an Assembly
Finds assemblies (finished goods tasks) by status, search text or sale.
- Find a Product
Finds products by name, SKU or ID.
- Find a Products Availability
Returns on-hand, allocated and available stock for products, per location.
- Find a Sale
Returns one sale by its ID, with its order, invoices and fulfilments.
- Find a Sale Credit Note
Returns a sale's credit notes.
- Find a Sale Extended
Finds sales by order number, customer, invoice number, reference, credit note number or status.
- Find a Sale Fulfilment
Returns a sale's fulfilments with their pick, pack and ship details.
- Find a Sale Invoice
Returns a sale's invoices.
- Find a Sale Payments
Returns the payments and refunds recorded on a sale.
- Update Customer
Updates an existing customer in Cin7 Core.
- Update Product
Updates an existing product in Cin7 Core.
- Update Sale
Updates the header of an existing sale in Cin7 Core.
- Update Supplier
Updates an existing supplier in Cin7 Core.
- Add event destination
Create a new event destination for receiving Stedi webhook events.
- Check eligibility
Runs a real-time eligibility and benefits check (X12 270/271) against a payer for a patient and returns the payer's coverage and benefits response.
- Delete event destination
Permanently deletes a Stedi event destination so it stops receiving events. This cannot be undone; to pause delivery instead, update the destination's status to DISABLED.
- Find payers by criteria
Searches the Stedi Payer Network for payers matching a name, payer ID or alias, optionally filtered by supported transaction types, coverage types, operating states and insurance programs. Returns matching payers ranked by relevance.
- Get event destination
Retrieve an event destination by id.
- Get payer
Retrieve a single payer record by id.
- List event destinations
Lists the event destinations configured in your Stedi account, optionally filtered by status or event type.
- List payers
Lists every payer Stedi supports, with payer IDs, aliases, supported transactions and enrollment requirements.
- Update event destination
Updates an existing Stedi event destination's name, URL, subscribed event types, description, status or concurrency limit. Fields left blank are not changed.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cin7 Core Inventory
Cin7 Core Inventory to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cin7 Core Inventory to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cin7 Core Inventory to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cin7 Core Inventory to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cin7 Core Inventory to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cin7 Core Inventory to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Stedi
Questions
Cin7 Core Inventory and Stedi, answered
What can start an automation from Cin7 Core Inventory?
Any of Cin7 Core Inventory's 13 triggers in the catalog, including New Customer / Updated Customer, New Payment, New Product / Updated Product and New Purchase / Updated Purchase. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Stedi when something happens in Cin7 Core Inventory?
Any of Stedi's 9 actions, including Update event destination, Add event destination, Check eligibility and Find payers by criteria. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Stedi to Cin7 Core Inventory?
Stedi has no triggers in the catalog today, so automations start in Cin7 Core Inventory. If you need the other direction, ask: your agent reads Stedi's API documentation and adds it.
Do I have to build a connector for Cin7 Core Inventory or Stedi?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Cin7 Core Inventory and Stedi without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.