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.
A routine is anything that should happen without someone asking. It has a trigger, an action, and who it reaches. Create one under Routines, describe it in a sentence with Describe it, or choose Repeat… on an answer.
On a schedule
Every day, every weekday, every week or every month, at a time you pick, in the workspace's time zone. The action is one of:
| Action | What happens |
|---|---|
| Ask a question | Asked fresh each time. The answer is checked like any other and kept in its conversation in Ask. |
| Send what OpenDash found | What's open in Insights and each person's open tasks, each with why. Nothing found, nothing sent. |
When something is found
Watch up to 50 verified metrics with a weekly or monthly grain. OpenDash checks each one as its period's data lands, and first right after you save the routine. It starts the routine when:
| Condition | Example |
|---|---|
| It's unusual | Signups dropped far outside their normal range. Sensitivity: lower, medium or higher. |
| It crosses a line | MRR falls below a value you set. |
| A goal is at risk | The forecast misses a goal. |
| Its data is missing | A table stopped updating. |
Choose At once or a Daily roundup, and Investigate first to have the analyst look into what changed before it tells anyone.
Watch on a metric answer adds that metric to the workspace's watching routine. Insights → Watching lists everything that's watched.
Delivery
- Email to the people you choose. Every email has a one-click unsubscribe.
- Slack to the channels you choose. See Slack and email.
Anyone can make a routine that only reaches themselves; a viewer's routine can only send what OpenDash found, since asking is for members. Routines that reach other people or channels are for owners and admins.
A routine that fails four runs in a row pauses itself, so a broken source doesn't flood anyone's inbox.
Insights and tasks
What a routine finds lands in Insights: anomalies, trends, crossed thresholds, goals at risk and data-quality problems.
- Investigate asks the analyst to explain it. The verdict reads Confirmed, Not confirmed, Explains it or Part of it, with the queries behind it.
- Create a task turns an insight into work: what to do, an optional due date, and how long to judge it over (one to six months). When it's done, OpenDash compares the outcome with where the trend was heading, in code, with no model involved.
- Owners and admins can dismiss an insight, with a reason.
Investigations and routines are paid from the workspace's background budget.
Connections
Connect services such as Jira, HubSpot or Fullstory over MCP, so the analyst and your dashboards can read what lives only there, and change things only when you allow each call.
Slack and email
Ask OpenDash from Slack with the same checked answers as the web app, and receive routines by Slack or email.