> 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/integrations/productivity-and-collaboration/slack-integration.md). # Slack PeakCommerce supports **Slack** so your team can stay on top of commerce — and act on it — without leaving their workspace. Slack becomes a thin, governed surface over the same commerce logic that runs in the app, not a separate set of rules. ## What it is Slack is a team messaging workspace. Connected to PeakCommerce, it serves two roles: a **notification channel** for commerce events, and a **command surface** where staff trigger common commerce tasks — for example a `/peak change-plan`-style slash command — that resolve to PeakCommerce's existing engines. ## What you can do with it * **Get notified where you already work** — post commerce events (new orders, cancellations, failed payments, high-value or flagged transactions) to the channels your team watches. * **Route approvals in place** — send actions that need sign-off — a discount above policy, a plan change — to Slack, where an approver acts without switching tools. * **Run actions from a slash command** — kick off common tasks such as changing a customer's plan. The request resolves against the same commerce engines the app uses, so the same profiles, policies, and pricing guardrails apply. ## How it fits You connect your Slack workspace and choose which events post to which channels and which actions require approval. Because Slack requests resolve against PeakCommerce's existing engines — profiles for who can act, policies for pricing limits, audiences and experiences for targeting — Slack never carries its own copy of the rules. The same governance that guards the app guards Slack. ## Who and when Most useful for support, sales, and revenue teams who live in Slack and need to see — or act on — commerce events quickly, while staying inside policy. ## Gotchas Slack inherits PeakCommerce's permissions: a user can only do in Slack what their profile already allows. A discount over policy still needs the same approval it would in the app. See also: [Productivity and collaboration integrations](/integrations/productivity-and-collaboration/productivity-and-collaboration.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 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/integrations/productivity-and-collaboration/slack-integration.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.