Integrations
Open Integrations → Browse in the workspace. Choose a provider, add its connection and follow its generated setup steps. The callback URLs and configuration belong to that particular connection.
Supported channels
Section titled “Supported channels”| Channel | Start or reply from the channel | Native approve/deny | Files |
|---|---|---|---|
| Slack | Supported app events and mapped threads | Yes | Workspace continuation |
| Telegram | Private bot text and mapped replies | Yes | Workspace continuation |
| Discord | Bot-DM /beepgrid and Reply forms |
Yes | Workspace continuation |
| Reply in the authenticated workspace | No native inbound reply | Workspace continuation | |
| Webhooks | Signed HTTP messages | Use the authenticated decision API | Workspace files/API |
WhatsApp, Teams, iMessage and other channel badges on the marketing site do not mean those native connectors are available in this release. More adapters are planned.
Setup has three parts
Section titled “Setup has three parts”- Connect the provider with your dedicated app or SMTP account.
- Link the person and destination where required. Use immutable provider IDs, not a matching display name or email guess.
- Test a real exchange. Send a diagnostic message, find it in the selected channel and reply using the supported path.
Installation and linking do not grant contact or decision permissions. Configure those separately in Access.
Read connection status
Section titled “Read connection status”Saved configuration is not proof of delivery. A provider can accept an outbound message while the connection is still verifying. An attributed return path proves the correlated exchange the engine observed.
Changing settings resets the diagnostic evidence. After reconnecting, run a fresh test. Disconnecting in Beepgrid stops its callbacks and queued sends; it does not uninstall the provider app or recall an already accepted message.