info Governed sends and provider read access work today. Automatic inbound chat depends on completing the Slack Events API ingress checklist for your workspace.
Available today#
| Action | Description |
|---|---|
| Post message | Send to any channel Sidekick is invited to |
| Read channel | Read recent messages from a channel |
| Thread reply | Reply into existing Slack threads |
| Notifications | Use Slack for approvals, alerts, and routed updates |
Inbound chat rollout#
Inbound Slack chat is available after the workspace admin completes the provider-side checklist:
- Connect the Slack workspace token
- Save the Slack signing secret
- Point the Events API to the LumenFlow-issued inbound endpoint
- Verify the target before enabling production automation
Setup#
- Go to Settings → Connections
- Click Add Connection → Slack
- Connect the Slack workspace you want Sidekick to use
- Confirm the team metadata and required scopes
- Save inbound verification settings if you want automatic chat ingress
Channel access#
Sidekick can only access channels it's been invited to. To add access to a new channel:
- Invite Sidekick to the channel in Slack (
/invite @LumenFlow) - The channel appears in LumenFlow automatically
Best practices#
- Use dedicated channels — create channels like #sidekick-updates for automated posts
- Set governance rules — require approval for messages to high-visibility channels
- Use threads — configure Sidekick to reply in threads to avoid channel noise
Message formatting#
Sidekick formats Slack messages using Slack's standard markdown syntax, including bold, italic, inline code, and blockquotes.
info Slack messages sent by Sidekick appear as the LumenFlow bot. Recipients can see which workspace triggered the message, and the resulting action stays visible in LumenFlow's proof trail.