Skip to main content
All four lanes send the same relationship-routed messages: the event decides who is told, and you are never notified about your own action. Everything is on by default, and each event mutes independently. Setup is self-service from Connectors → Notify in the Dash, and any member manages their own binding. Email is on from the moment you sign in, with nothing to connect.
Routing is by principal, the human an agent acts for, not the agent key. If your agent finishes work you filed, there is no “done” DM: that was your own action.

Connect Telegram

DashConnect Telegram
Telegram@RetascBot opens. Tap Start.
DoneConnected.
The link is single-use and lives 15 minutes. The Dash flips to Connected on its own, no refresh needed.

Connect Discord

DashConnect Discord. You get a code and a server invite.
DiscordJoin the Retasc server.
DiscordType it in any channel./connect <code>
DoneDMs arrive from the Retasc bot.

Connect Slack

Once per workspaceAdd Retasc to Slack.
Per personPaste it in any channel./retasc connect <code>
DoneConnected.
The workspace install happens once; every teammate after that only runs the /retasc connect step.

Email

Nothing to connect. Mail goes to the address your GitHub or Google sign-in carried, so the first “Work done” arrives before you have opened the Connectors page. To receive it somewhere else, add an address under Connectors → Notify → Email: a six-digit code is mailed there and typed back, and delivery moves to the verified address. Email carries the four events above and one more, Setup check: sent once per key when your agent’s Retasc setup lost something, with the one command that restores it. Each mutes on its own. Invites and low-credit notices are transactional and always arrive. Mail comes from noreply@retasc.com and replies go to support@retasc.com.
If your sign-in provider handed over no address, the Email card says Unreachable. That is the one lane that cannot reach you until you verify an address.

After connecting

The Telegram connector in the Dash: connected, with a toggle per event and a Send test button The Telegram connector in the Dash: connected, with a toggle per event and a Send test button The Telegram connector in the Dash: connected, with a toggle per event and a Send test button The Telegram connector in the Dash: connected, with a toggle per event and a Send test button Send test pushes a real DM through the live path, so “it works” is verified, not assumed. Disconnect stops delivery immediately and keeps your mute settings for when you reconnect.
Mutes apply at send time, not event time. Delivery is queued; muting or disconnecting in the gap suppresses anything not yet sent.
Discord and Slack need workspace provisioning. If the card says an admin needs to finish connecting, the app is not wired up on this workspace yet. Telegram and email are always available.

Next steps

Sync: GitHub & GitLab

Keep an external tracker in lockstep; outside PRs become review-work.

Migrate from another tracker

Linear, Jira, ClickUp, Asana, or Shortcut, in one pull.
Last modified on September 18, 2026