Integration
Connect Commerce Layer to Pylon
When New Attachment fires in Commerce Layer, your agent runs Add internal note to issue in Pylon. 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 Layer and Pylon 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 Layer can start in Pylon
When New Attachment in Commerce Layer
then Add internal note to issue in Pylon
When New Customer in Commerce Layer
then Add task in Pylon
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 Layer and Pylon
Triggers and actions 13 triggers · 53 actions
Trigger
New AttachmentTriggers when a new Attachment is created.
Trigger
New CustomerTriggers when a new Customer is created.
Trigger
New Customer Address EventTriggers when a customer address is created.
Trigger
New Customer Password Reset EventTriggers when a customer password reset is requested.
Trigger
New Customer Subscription EventTriggers when a given customer_subscription event (one of create or destroy) is fired.
Trigger
New PriceTriggers when a new Price is created.
Trigger
New Price ImportFires when a new price import is created in Commerce Layer.
Trigger
New Price ListTriggers when a new Price List is created.
Trigger
New Shipping CategoryTriggers when a Shipping Category is created.
Trigger
New SKUTriggers when a new SKU is created.
Trigger
New SKU ImportTriggers when a new SKU import is created.
Trigger
New Stock Item ImportTriggers when a new Stock Item import is created.
Trigger
New Stock Transfer EventTriggers when a given stock transfer event (one of create, upocoming, picking, in_transit, complete, cancel is fired).
Action
Add Customer AddressAdds an existing address to a customer's address book.
Action
Add Customer Password ResetRequests a password reset for a customer, returning the reset token to send them.
Action
Add Customer SubscriptionSubscribes a customer email to a list, identified by a reference such as a newsletter id.
Action
Add Stock TransferMoves a quantity of a SKU from one stock location to another.
Action
Balance Change Gift CardChange balance of a gift card.
Action
Create AddressCreates a postal address that can be attached to customers, orders and stock locations.
Action
Create AttachmentCreates a new Attachment.
Action
Create CustomerCreates a new Customer.
Action
Create Gift CardCreates a new Gift Card.
Action
Create Price ImportCreates a new Price Import.
Action
Create Price ListCreates a new Price List.
Action
Create SKUCreates a new SKU.
Action
Find AttachmentFinds a Attachment by name.
Action
Find CustomerFinds a customer by id or reference.
Action
Find Gift CardFinds a gift card by id or reference.
Action
Find PriceFinds a price by price list.
Action
Find Price ImportFinds a Price Import by status.
Action
Find Price ListFinds a Price List by name.
Action
Find Shipping CategoryFinds an Shipping Category by name.
Action
Find SKUFinds an SKU by code.
Action
Find SKU ImportFinds an SKU Import by status.
Action
Find Stock Item ImportFinds a Stock Item Import by status.
Action
Get AddressRetrieves one address by id.
Action
Get Customer AddressRetrieves one customer address link by id.
Action
Get Customer Password ResetRetrieves a customer password reset by id, returning customer_email, reset_password_token and reset_password_at.
Action
Get Customer SubscriptionRetrieves one customer subscription by id.
Action
Get Stock TransferRetrieves one stock transfer by id.
Action
Update Customer ReferenceUpdate customer data setting external identifier.
Action
Add internal note to issueAdds an internal note to a Pylon issue. Internal notes are not visible to the requester.
Action
Add tagCreates a new tag in Pylon that can be applied to accounts, articles or issues.
Action
Add taskCreates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.
Action
Create AccountCreates a new customer account in Pylon with its name, domains, owner, tags and other details.
Action
Create Account ActivityCreates a custom activity on a Pylon account's timeline.
Action
Create Call RecordingCreates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon.
Action
Delete accountPermanently deletes a Pylon account by its ID or external ID.
Action
Delete issuePermanently deletes an issue in Pylon.
Action
Find Account by NameFinds Pylon accounts by name, by exact or partial match, returning the matching accounts.
Action
Find contacts by criteriaReturns the contacts that match the specified search text and/or filter.
Action
Find issues by criteriaReturns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.
Action
Get accountReturns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.
Action
Get contactReturns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.
Action
Get issueReturns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.
Action
Get userReturns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.
Action
Get UsersReturns the users in your Pylon organization, optionally including deactivated users.
Action
List accountsReturns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.
Action
List contactsReturns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.
Action
List tagsReturns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.
Action
List teamsReturns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.
Action
Reply to issueSends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.
Action
Update AccountUpdates an existing Pylon account. Only the fields you fill in are changed.
Action
Update contactUpdates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.
Action
Update issueUpdates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed.
Action
Update Issue FollowersAdds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers.
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 Layer
Commerce Layer to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Commerce Layer to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Commerce Layer to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Commerce Layer to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Commerce Layer to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Commerce Layer to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Pylon
HubSpot to PylonHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PylonSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PylonSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PylonGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PylonGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PylonGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Commerce Layer and Pylon, answered
What can start an automation from Commerce Layer?
Any of Commerce Layer's 13 triggers in the catalog, including New Attachment, New Customer, New Customer Address Event and New Customer Password Reset Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pylon when something happens in Commerce Layer?
Any of Pylon's 25 actions, including Create Account, Create Account Activity, Create Call Recording and Update Account. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pylon to Commerce Layer?
Pylon has no triggers in the catalog today, so automations start in Commerce Layer. If you need the other direction, ask: your agent reads Pylon's API documentation and adds it.
Do I have to build a connector for Commerce Layer or Pylon?
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 Layer and Pylon 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.