Salla merchant MCP connection
Authorize Salla and approve selected actions from the official merchant MCP server.
Use a test channel or sample conversation first. Confirm the visible result in ValueChat before applying the setup to production traffic.
How it works
- 01
Connect
Connect. In Integrations choose Salla, sign in through Salla and grant access. This uses the merchant MCP server, not a developer tool for managing Salla partner applications.
- 02
Discovery
Discovery. Manage the connection to discover its current tool catalog and review compatible schemas. Discovery alone gives no agent execution permission; approve only the needed actions.
- 03
Reuse
Reuse. Select the authorized connection and permitted actions in an agent app skill or workflow integration step. Multiple agents can reuse the same store connection while retaining their own permissions.
- 04
Boundary
Boundary. The exact live actions depend on the merchant catalog and compatible schemas. Do not promise a fixed list of every Salla API operation or assume that arbitrary MCP tools are supported.
- 05
Customer privacy
Customer privacy. This connector does not implement Salla buyer/order ownership verification. Do not grant unrestricted private customer/order lookup or merchant administration to public-facing conversations.
- 06
Lifecycle
Lifecycle. Reconnect changes the authorization/catalog revision, so review saved bindings. No Salla order-event webhook trigger is created by this connection. Real merchant consent and operations need store-specific acceptance.
What to verify
✓The expected channel, conversation, contact or execution is visible.
✓The assigned person or agent matches the routing rule.
✓No customer-facing message claims an action that failed.
✓Activity or execution history contains enough context to investigate.
Collect the workspace, channel, conversation and execution identifiers, then contact support@valuechat.app. Never send API keys or passwords.