AeionClaw + Slack
AeionClaw's Reaction Engine and scheduled workflows can push formatted alerts straight into a Slack channel — no custom Slack app to build, no bot to install. Point a Slack incoming webhook URL at a Claw reaction and Aeion posts a Block Kit–formatted message the moment the trigger condition fires. This is one-way delivery: Aeion → Slack. There's no inbound listener, so Claw can't see channel messages, respond to @mentions, run slash commands, or hold a DM conversation in Slack today.
How It Actually Works
`
Setup Walkthrough
```bash
FAQ
Not today. Claw's Slack integration is a one-way outbound webhook — you generate a Slack incoming-webhook URL and give it to a Claw reaction or notification target. There's no OAuth flow, bot identity, or app to add to your workspace for Claw specifically.
Not currently — Claw has no Slack Events API subscription, so it can't see channel messages or mentions. Everything is Aeion-event-triggered, not Slack-message-triggered.
Not available today. Both would require a registered Slack app with command endpoints, which doesn't exist for Claw yet.
Anything a Claw Reaction or scheduled workflow is configured to push — stalled-deal alerts, escalated monitoring alerts, digest-style summaries composed by a Claw persona — delivered as a formatted Slack message via the webhook.
No — Aeion's webhook delivery layer detects the Slack hostname and formats a standard Block Kit message (title + body) automatically. You only supply the webhook URL and message content.
That's Aeion Connect's Slack integration — a real OAuth-based workspace connection for reading/sending support conversations. It's a separate feature from Claw's outbound-only webhook alerts.
Yes — see `microsoft-teams-claw-bot`. Same webhook-only mechanism, Teams Adaptive Card formatting instead of Block Kit.
A conversational, installable Slack app (DMs, mentions, slash commands) isn't shipped yet. Talk to your Aeion contact if this is a blocker for your rollout.