Skip to main content
All three connectors send the same relationship-routed DMs: the event decides who is told, and you are never notified about your own action. Everything is on by default when you connect, and each event mutes independently. Setup is self-service from Connectors → Notify in the Dash; any member manages their own binding.
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

1 · DashConnect Telegram
→
2 · Telegramopens @RetascBot, tap Start
→
3Connected
The link is single-use and lives 15 minutes. The Dash flips to Connected on its own, no refresh needed.

​
Connect Discord

1 · DashConnect Discord: a code + server invite
→
2 · Discordjoin the Retasc server
→
3type /connect <code>
→
4DMs arrive from the Retasc bot

​
Connect Slack

1 · once per workspaceAdd Retasc to Slack
→
2 · per personpaste /retasc connect <code> in any channel
→
3Connected
The workspace install happens once; every teammate after that only runs the /retasc connect step.

​
After connecting

dash.retasc.com/connectors
Telegram Connected
Work done
Assigned to you
Review requested
Work canceled
Send test
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 is 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 August 6, 2026