Integration
Connect Commerce Tools to Peaka
When New customer fires in Commerce Tools, your agent runs Run Peaka Query (With Line Item Support) in Peaka. 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 Commerce Tools and Peaka 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 Commerce Tools can start in Peaka
When New customer in Commerce Tools
then Run Peaka Query (With Line Item Support) in Peaka
When New order in Commerce Tools
then List projects in Peaka
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 Commerce Tools and Peaka
Triggers and actions 2 triggers · 31 actions
Trigger
New customerTriggers when a new customer is created in your commercetools project.
Trigger
New orderTriggers when a new order is created in the commercetools project.
Action
Add cartCreates a new shopping cart in your commercetools project, optionally with line items, customer, addresses and discount codes.
Action
Add categoryCreates a category in your commercetools project for organizing products.
Action
Add customerCreates a customer in your commercetools project and returns the new customer record.
Action
Add order from cartCreates an order from an existing cart, optionally setting its order number and initial order, payment and shipment states.
Action
Add productCreates a product in your commercetools project with its product type, name, slug and optional variants, prices, categories and attributes.
Action
Delete customerDeletes a customer, optionally erasing all of their related personal data. Returns the deleted customer.
Action
Delete productDeletes a product from the catalog and returns the product as it was when deleted.
Action
Find categoriesFinds categories in your commercetools project that match a filter, such as a key, slug or name.
Action
Find customersFinds customers matching a filter condition, such as an email address or last name.
Action
Find inventory entriesReturns the inventory entries (stock quantities per SKU and supply channel) that match a filter.
Action
Find ordersFinds orders in the commercetools project that match a filter condition.
Action
Find productsFinds products in your commercetools project that match a filter condition, such as a product key or name.
Action
Get cartReturns a cart by its id, including its line items, totals, addresses and state.
Action
Get customerReturns a single customer by its id, including addresses and custom fields.
Action
Get orderReturns an order by its id, including line items, totals, state and custom fields.
Action
Get productReturns a product by its id, including its current and staged data, variants and prices.
Action
Update cartUpdates a cart by applying one or more update actions, such as adding line items or setting the shipping address, and returns the updated cart.
Action
Update customerApplies one or more update actions to an existing customer, such as changing their email, name or addresses, and returns the updated customer.
Action
Update inventory entryUpdates an inventory entry, for example adding, removing or setting its stock quantity, and returns the updated entry.
Action
Update orderUpdates an order by applying one or more update actions, such as changing its order, shipment or payment state.
Action
Update productUpdates a product by applying one or more update actions, and returns the updated product.
Action
Add connectionCreates a new data source connection in a Peaka project.
Action
Add queryCreates a saved SQL query (plain or materialized) in a Peaka project, optionally inside a folder.
Action
Delete connectionDeletes a connection from a Peaka project. Any catalogs using this connection lose access to their data source.
Action
Delete queryPermanently deletes a saved query from a Peaka project.
Action
Get queryReturns a single saved query in a Peaka project by its ID, including its SQL, type, schedule and folder location.
Action
List connectionsLists all connections (authenticated links to external data sources) in a Peaka project.
Action
List projectsLists all projects within a Peaka workspace.
Action
List queriesReturns all saved queries in a Peaka project, including each query's folder path when it sits in a folder.
Action
Run Peaka Query (With Line Item Support)Runs a SQL statement, a saved query, or a query builder request in a Peaka project and returns the result rows as line items.
Action
Update queryUpdates the display name, SQL, type or schedule of an existing Peaka query. Fields left blank keep their current values.
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 Commerce Tools
Commerce Tools to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Commerce Tools to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Commerce Tools to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Commerce Tools to Google SheetsGoogle Sheets
Commerce Tools to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Commerce Tools to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Peaka
HubSpot to PeakaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PeakaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PeakaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PeakaGoogle Sheets
Gmail to PeakaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PeakaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Commerce Tools and Peaka, answered
What can start an automation from Commerce Tools?
Any of Commerce Tools's 2 triggers in the catalog, including New customer and New order. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Peaka when something happens in Commerce Tools?
Any of Peaka's 10 actions, including Update query, Add connection, Add query and Get query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Peaka to Commerce Tools?
Peaka has no triggers in the catalog today, so automations start in Commerce Tools. If you need the other direction, ask: your agent reads Peaka's API documentation and adds it.
Do I have to build a connector for Commerce Tools or Peaka?
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 Commerce Tools and Peaka 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.