Integrations
Integrations route your project's inbox alerts — raids, flagged joins, agent health, billing, X signals, and more — to the tools your team already watches. Connect a destination once, then choose which events land in each channel.
You'll find the page in your project sidebar as Integrations. Only the project Owner and Project Admins can manage integrations; other members see "You don't have permission to manage this project's integrations."
Slack
Slack is the integration you can connect today: "Send inbox alerts — raids, flagged joins, agent health, and billing — to the Slack channels your team already watches."
Connecting a workspace
Slack connects through OAuth — you never paste a webhook URL:
- On the Integrations page, select Connect on the Slack card.
- Approve the authorization in Slack. You're returned with the banner "Slack workspace connected. Add a channel below."
- Select Add channel and pick a channel from your workspace in the picker.
Private channels appear in the picker only after you invite the Fren One agent to them in Slack.
There's a fixed cap on destinations — the page shows "You can connect up to {max} Slack channels." Workspaces connected before the OAuth flow may show "Slack · delivering via legacy webhooks"; they keep working.
Choosing what each channel receives
Each connected channel shows who connected it and when. Select Manage to open the Event routing modal — "Choose which events are delivered to {channel}." Events are grouped into ten categories, each a checkbox with Select all / Select none and an "N of M selected" count:
- Moderation & safety
- Agent health
- Members
- Insights
- Support
- X
- Billing & credits
- Governance & coverage
- Reports
- Backups
When your project has X accounts, the X category also shows an "X account scope" control: route X alerts from All X accounts or only Specific accounts — useful for giving each brand account its own Slack channel.
Per-channel controls
| Control | What it does |
|---|---|
| Send test | Delivers a test message ("Test message sent to {channel}."). |
| Active / Paused | Pauses delivery to the channel without losing its event routing. |
| Remove channel | Stops delivering alerts to the channel (asks for confirmation). |
| Disconnect | Disconnects the whole Slack workspace. |
Slack alerts for X mentions include a "Generate reply" action that drafts a response using the account's Brand Voice settings. Slack messages are English-only today.
Coming soon
Three more destinations are listed on the page but are placeholders — their Connect buttons are disabled and you can't set them up yet:
| Destination | Description |
|---|---|
| Discord channel | "Post project alerts to your team's Discord server." |
| Telegram channel | "Route alerts to a private Telegram channel or group." |
| Webhooks | "Send every inbox event to your own endpoint as JSON." |
How delivery works
Every alert lands in your project inbox first — the inbox is the source of truth. From there, each enabled Slack channel that's subscribed to the alert's event category receives a copy.
Slack routing is separate from personal notifications: each member's own web and email preferences live in Manage notifications and aren't affected by what you route to Slack. Channel destinations like Slack are opt-in per project — nothing is delivered until an Owner or Project Admin connects a destination and picks its events.
Next steps
- 📡 Listening — configure the X keywords, accounts, and signals you can route here
- 🎙️ Brand Voice — the settings behind the Slack "Generate reply" action
- Projects — who counts as an Owner or Project Admin