Slack and email
Ask OpenDash from Slack with the same checked answers as the web app, and receive routines by Slack or email.
Set up Slack
Owners and admins connect Slack under Settings → Slack. Each OpenDash workspace connects one Slack workspace.
Create the app from OpenDash's manifest
On a self-hosted instance, print a manifest for your address:
pnpm slack:manifest https://opendash.example.com --socketCreate a Slack app from it. With --socket it uses Socket Mode, so Slack needs no public address to send events to.
Put its keys in OpenDash's settings
From the app's Basic Information, set SLACK_CLIENT_ID, SLACK_CLIENT_SECRET and SLACK_SIGNING_SECRET. For Socket Mode, also create an app-level token with connections:write and set it as SLACK_APP_TOKEN.
Restart OpenDash
Both web and worker read the keys at start.
Add to Slack
Back in Settings → Slack, choose Add to Slack.
Ask from Slack
Ask in a direct message, in the Agents tab, or by @mentioning the bot in a channel. In a channel thread, mention the bot again for follow-ups. A message sent while it's working is added to what it's working on.
The first time someone asks, they get a private link to connect their Slack account to OpenDash. It works once, for 10 minutes, and their Slack email must match their OpenDash account. They can unlink under Settings → Security.
Replies
Replies carry the same checks as the web app, in their footer:
- Verified from definitions an admin approved: the metric path.
- Every number checked against its query: the gate passed.
- Unverified: …: what couldn't be checked.
Answers with numbers attach a PDF and the cited rows as CSV. Feedback, Investigate and Dismiss on findings, and learning approvals all work right in Slack.
You can attach text or Markdown files (up to three, 1 MB each) for context.
In Slack the analyst uses only connected services shared with everyone; a call that needs your sign-in or approval asks you to allow it in OpenDash. Dashboards are built in OpenDash, not from Slack.
OpenDash sends two kinds of email:
- Sign-in and account email (sign-up, sign-in links, password reset), which every instance needs. Configure Resend or any SMTP server; see Configuration.
- Routine deliveries: a scheduled question's answer, what OpenDash found, a finding told at once or the daily roundup, and a notice to a routine's owner when it paused itself, to the people a routine names. Every one has a one-click unsubscribe.
Routines and insights
Make things happen on their own. Ask a question every Monday, get what OpenDash found, or watch your metrics and get told what moved and why.
Models and providers
Which models OpenDash offers, how to use the deployment's keys or your own provider per workspace, and how spend limits work.