> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/guides/orders/sync-orders-with-external-services/automated-orders-sync.md). # Automated orders sync While it's possible to receive orders and sync their details manually, automated solutions are more reliable and consistent. Check out the available options below. ### Free Zapier integration This integration allows you to automatically sync new orders from your store to a Google spreadsheet **without any coding**. You can select the desired fields like order statuses, total, IDs, shipping details, etc. Find the instructions in the App Market card: {% embed url="" %} ### Webhook automation Webhooks allow you to receive automatic notifications about different events in the store. You can build a self-hosted endpoint listening to incoming POST requests from Ecwid API and automate getting full order details upon receiving `order.created` webhooks. From here, you can build any automation with the proper knowledge and dev skills. Learn more about building [webhook automations for order sync](/webhook-automations/webhook-flow-examples/export-new-orders.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ecwid.com/guides/orders/sync-orders-with-external-services/automated-orders-sync.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.