Use Riley anywhere

Use Riley in Slack.

one workspace · same approval gate · same proof

Optional delivery channel: receipts, approval requests, and alerts can land in Slack. It is also a data source Riley can read and analyze.

LiveAll surfaces

What it is

Optional delivery channel: receipts, approval requests, and alerts can land in Slack. It is also a data source Riley can read and analyze.

What Riley can do here

Ask for work in plain language and Riley does it with the same tools, memory, and rules as everywhere else. Reading and drafting happen freely; anything that writes outside your workspace waits for your approval.

Easy setup

No code required.

Install the Riley Slack app from your dashboard.
Invite Riley to the channels you want it to read or deliver to.
Choose which receipts, approvals, and alerts land in Slack from Settings.

Advanced setup

For technical users.

Slack is a first-party connection, not an MCP client; no key or endpoint needed.

Full protocol notes, the tool list, and supported methods live on the developers page.

Permission model

Riley only sees channels you invite it into; approvals happen from the notification or the dashboard.

Proof captured

Receipts and approvals delivered to Slack come from the same recorded work you see in the dashboard.

Security

Keys and access.

This surface is a first-party connection, so there is no key to mint or paste. Riley only reaches what you grant, and every external write still passes through your approvals queue. You can disconnect at any time from Settings.

See the security page for the full permission model and proof receipts for how work is recorded.