EasyOrders connection and actions

Connect an EasyOrders store and distinguish public catalog tools from administrator operations.

How it works

1. 01

   Connect

   Connect. Use the authorized installation flow and finish it from the initiating administrator session, or supply a validated Public API key through the manual alternative. Credentials remain encrypted; an installation callback alone does not activate a connection.

2. 02

   Customer conversations

   Customer conversations. Agents and conversation workflows currently receive four public catalog reads: list/get products and list/get categories.

3. 03

   Administrator catalog

   Administrator catalog. The full fifteen-action catalog also includes product creation/update, product/variant stock updates, category creation/update, order lookup/by number, status changes, order notes and shipping configuration.

4. 04

   Enforced limits

   Enforced limits. The remaining eleven actions are administrator-test-only and cannot be exposed to a customer by changing prompt instructions or invoking a nested workflow. Server-verified customer ownership is required before broadening access.

5. 05

   Effects

   Effects. A paid/refunded status label does not execute or verify a payment/refund. Shipping updates replace the configured city/cost list. Product editing covers the supported contract fields, not every merchant UI option.

6. 06

   Protocol and readiness

   Protocol and readiness. This connector uses the EasyOrders REST API, not a claimed official MCP server. It adds no order-webhook triggers. Real merchant authorization and operations still need a dedicated store test; uncertain writes are not automatically retried.

What to verify