Aeion CRM + Slack
Today, CRM deal-stage-change events (`crm.deal.stage_changed`, `crm.deal.won`, `crm.deal.lost`) route to in-app notifications for the deal owner — not to Slack. Aeion's notifications platform has a generic Slack-incoming-webhook channel (Block Kit formatting) that a tenant can configure for other notification types, but it isn't wired to CRM deal events out of the box, and there's no dedicated Slack bot app, slash commands, or interactive "mark won" buttons in the product today. This page is deliberately specific about what exists vs. what would need to be built.
What's Real Today
- CRM emits real events on deal changes —
crm.deal.stage_changed,crm.deal.won, andcrm.deal.lostfire from the deal service whenever a deal's stage changes. Today's built-in subscriber turnscrm.deal.stage_changedinto an in-app notification for the deal's owner (channel:in_app) — it does not post anywhere else by default.
What's Not Built
None of the following exist in the codebase today — no bot app, no slash-command handler, no interactive Block Kit buttons, no scheduled digest job wired to Slack, and no Slack-user-to-Aeion-user mapping:
Common Gotchas
- Deal-stage-change notifications default to in-app, not Slack — if you're expecting a Slack ping the moment a deal moves stage, it isn't there without you building the webhook wiring described above.
FAQ
Not out of the box. You can configure a Slack incoming-webhook URL in the generic notifications webhook channel and wire a Blueprint automation to post on `crm.deal.won` — that requires manual setup, not a toggle.
No, not today.
No — there's no interactive-component handler for Slack in the product.
Talk to the CRM team for current roadmap status — it isn't shipped today.
Same generic webhook channel supports a Teams-formatted payload; same caveat — no bot app, no slash commands.