> 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](https://docs.peakcommerce.com/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peakcommerce.com/product/using-peakcommerce/workflows-and-actions.md?ask=<question>&goal=<user_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.
