Integration
Connect Salla and Trengo
When something happens in Salla or Trengo, your agent does the next thing in the other. Describe it 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 Salla and Trengo to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Salla and Trengo can do together
From Salla to Trengo
When Product Created in Salla
then Add internal note to ticket in Trengo
From Trengo to Salla
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 Salla and Trengo
Triggers and actions 7 triggers · 35 actions
- Customer Registered
Fires instantly when a new customer registers in (or is added to) the Salla store.
- Order Placed
Triggers when a new order is placed.
- Product Created
Fires when a new product is created in the Salla store (product.created webhook).
- Product Updated
Fires when a product in the Salla store is updated.
- Add customer
Creates a new customer in the Salla store.
- Add order
Creates an order in the Salla store (one-time or subscription).
- Add order history
Appends a note to an order's history in Salla.
- Add product tag
Creates a product tag in the Salla store.
- Create Product
Creates a product in the Salla store.
- Delete customer
Deletes a customer from the Salla store's customer list.
- Delete Product
Deletes a product from the Salla store by its id.
- Find a Category
Search the store's categories by name keyword and/or category IDs.
- Find a Customer
Finds customers in the store whose mobile number, email or name matches a keyword.
- Find a Product
Returns the products whose name or SKU matches the keyword, optionally narrowed by status and category.
- Get customer
Returns a single Salla customer's details by id.
- Get order
Returns the full details of a single Salla order by its order id.
- Get product
Get product details by id.
- List customers
Lists the customers in the Salla store, optionally narrowed by a keyword or a creation-date range.
- List products
Lists the products in the Salla store, optionally narrowed by keyword, status or category. Returns the first page of results.
- Update customer
Updates an existing customer in a Salla store. Only the fields you fill in are changed; blank fields keep their current values.
- Update Order Status
Changes the status of a Salla order, either to one of Salla's built-in statuses or to a custom order sub-status.
- Update Product
Updates an existing product in the Salla store. Only the fields you fill in are changed.
- Update Product Quantity
Sets, adds to or subtracts from the stock quantity of one product or variant, identified by product id, variant id or SKU.
- Upload Product Image
Attaches one image to a Salla product, either from a public image link or by uploading an image file. A product can hold up to 10 images.
- New Internal Note
Fires when an internal note is added to a Trengo ticket.
- New Outbound Message
Triggers when an outbound message is created.
- Ticket Label Added
Triggers when a label is added to a conversation.
- Add internal note to ticket
Adds an internal note (visible only to agents) to a Trengo ticket.
- Add ticket
Create a new support ticket.
- Add ticket label
Attaches an existing label to a Trengo ticket.
- Create a Contact
Creates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
- Create webhook
Subscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
- Delete contact
Delete a contact by id.
- Delete ticket
Delete a ticket by id.
- Find a Contact
Returns the Trengo contacts that match the search term.
- Get contact
Retrieve a single Trengo contact by its id.
- Get webhook
Fetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
- List contacts
List all contacts.
- List labels
Lists the ticket labels defined in the Trengo account (first page).
- List tickets
Returns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
- Send a Message
Sends a reply message on an existing Trengo ticket, over the ticket's own channel.
- Update contact
Update an existing contact by id.
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 Salla
Salla to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Salla to StripeStripe is a payment processing platform for online businesses.
Salla to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Salla to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Salla to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Salla to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
More into Trengo
HubSpot to TrengoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TrengoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to TrengoGoogle Sheets
Gmail to TrengoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TrengoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Salla and Trengo, answered
What can start an automation from Salla?
Any of Salla's 4 triggers in the catalog, including Product Created, Product Updated, Customer Registered and Order Placed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Trengo when something happens in Salla?
Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to Salla?
Yes. When something happens in Trengo, your agent can act in Salla too. This page covers both directions: Trengo's triggers and Salla's actions are listed here as well.
Do I have to build a connector for Salla or Trengo?
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.
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.