Send Store MCP Notifications to Slack or Discord

Slack and Discord destinations send supported notices to a channel you control; they do not add provider order-event ingestion.

Prerequisites

Use a plan that includes Slack or Discord and an incoming-webhook URL obtained through your workspace’s approved administration process. Keep that URL secret. Consult the destination provider’s current administration guide if you cannot create a webhook.

Steps

Open Notifications and choose Slack or Discord. Paste the incoming-webhook URL only into the browser form.
Choose available event types and the intended store scope. Save and enable the destination.
Run a destination test and confirm the marked message in the intended channel.
Inspect last delivery and failure state. If only tests arrive, check provider event coverage and subscription filters.

Safe example

The example uses synthetic names. Select your own authorized store and verify every identifier before a write.

Inspect my notification destination health and supported event types. Do not print webhook URLs or signing secrets.

You’re done when…

Expect a test message in the correct channel and updated destination health. A successful test establishes endpoint delivery only.

Limitations

URLs must be accepted HTTPS destinations; redirects are not followed. Provider timeout, 429 or server failure can trigger retry. Duplicate delivery remains possible. eBay, Square and WooCommerce do not currently emit Store MCP order events.