> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/workflows-and-actions.md). # Workflows & Automation PeakCommerce keeps commerce behaving consistently — pricing, plan dependencies, territories, and policy guardrails — without custom code, through **Rules & Automation**. These engines evaluate automatically as customers, CSRs, partners, and AI agents move through journeys, so the same rules apply no matter who is transacting or which channel they use. The engines include **Business Rules** (trigger actions and enforce conditions in a flow), **Plan Dependencies** (what can be bought together or requires what), **Pricing Rules** (discounts, tiers, and promotions within guardrails), **Territory Rules** (route and assign ownership by region or segment), and the **Policy Engine** (the hard ceilings, such as a maximum discount, that no channel can exceed). * [Rules & Automation](/product/using-peakcommerce/workflows-and-actions/workflows.md) — what each engine does and how they fit together > For multi-system automation (for example post-cancellation billing tasks), PeakCommerce generally recommends building those workflows in your system of record — Zuora or Salesforce — when it offers a workflow module. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/using-peakcommerce/workflows-and-actions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.