# Ecwid integrations: orders and products > Create an order, create a product and create a category in Ecwid, and start a workflow when Ecwid sends “Order created”. **Canonical page:** https://tray.ai/connectors/ecwid-integrations/ **Categories:** E-commerce **Connects through:** HTTP Connector ## Overview Ecwid is an ecommerce platform for building an online store or adding one to an existing website, covering products, orders, customers, and discounts. Tray.ai connects to Ecwid through the HTTP Connector, so your workflows can call the Ecwid API alongside the rest of your stack. ## Use cases ### Orders Read, create, update, and delete orders in Ecwid from any Tray.ai workflow. The Ecwid API covers calls such as search orders and get an order. - Search orders - Get an order - Create an order ### Products Read, create, and update products in Ecwid from any Tray.ai workflow. The Ecwid API covers calls such as search products and get a product. - Search products - Get a product - Create a product ### Categories Read, create, update, and delete categories in Ecwid from any Tray.ai workflow. The Ecwid API covers calls such as search categories and create a category. - Search categories - Create a category - Update a category ### Customers Read, create, update, and delete customers in Ecwid from any Tray.ai workflow. The Ecwid API covers calls such as search customers and create a customer. - Search customers - Create a customer - Update a customer ### Abandoned carts Read and update abandoned carts in Ecwid from any Tray.ai workflow. The Ecwid API covers calls such as search abandoned carts and update an abandoned cart. - Search abandoned carts - Update an abandoned cart - Convert a cart to an order ### Discount coupons Read and update discount coupons in Ecwid from any Tray.ai workflow. The Ecwid API covers calls such as search discount coupons and update a discount coupon. - Search discount coupons - Update a discount coupon ## Challenges Tray.ai solves ### Keeping Ecwid credentials out of logs A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots. **How Tray.ai helps:** Store Ecwid credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output. ### Going from the Ecwid API docs to a working call Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand. **How Tray.ai helps:** Paste a cURL example from the Ecwid API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you. ### Handling files and non-JSON responses Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload. **How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads. ## Frequently asked questions ### Does Tray.ai connect to Ecwid? Yes. Tray.ai connects to Ecwid through the HTTP Connector, which calls the Ecwid API directly. Any call the Ecwid API documents can run as a step in a Tray.ai workflow. ### How does Tray.ai authenticate with Ecwid? The Ecwid API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request. ### Can I get a dedicated Ecwid connector? Ecwid runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Ecwid connector from the Ecwid API. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/