Weekday executive KPI snapshot from Looker into Slack
Every weekday at 8am, your leadership channel gets a short plain-English read on revenue, signups, and support volume, covering only what actually moved.
Looker
Slack BotOperationsDaily DigestsAI ReportsEvery weekday at 8am, post a short executive snapshot of yesterday's business performance to our leadership Slack channel.
Start in Looker. Run the saved Looks that cover our headline metrics: revenue, new signups, and support ticket volume. Use Run Look for each one. If I have given you Look names rather than ids, use Search Looks first to find the right Look, and make sure you matched the one I meant before running it.
For each metric I need three numbers: yesterday's value, the day before it for day-over-day movement, and the same weekday last week for week-over-week movement. If a Look already returns a trend or a prior-period row, read the comparison straight out of those results. If it only returns a single current value, use Run Query to re-run the same underlying query with the date filter shifted to the comparison period. Express movement as both the absolute change and the percentage change.
Then write the snapshot in plain English, under ten lines in total. Lead with the metric that moved most by percentage change, not with whichever Look happened to run first. Skip anything that is essentially flat, meaning less than roughly 2 percent movement in either direction, so the post stays worth reading. After the numbers, add one or two callouts on what actually changed: a signup spike that traces back to a single channel, support volume climbing three days in a row, revenue held up by one large order. Write for executives who have not opened a dashboard: no metric jargon, no Looker field names, and no raw table dumps.
Post the finished snapshot to our leadership Slack channel with the Slack Bot integration, using Send a Message. Send it as one message rather than a thread of separate metrics.
Do not silently drop a metric. If a Look fails or comes back with no rows, still post the snapshot with the metrics you did get, and add a closing line naming what is missing and why, so a broken report never reads as a quiet day. If every metric came in flat, post a single line saying exactly that instead of padding the message.
What does this prompt do?
- Runs your saved Looker reports for revenue, new signups, and support volume every weekday morning, before the leadership team logs on.
- Works out what changed since yesterday and since the same day last week, so the numbers arrive with context instead of as bare totals.
- Writes a snapshot of under ten lines that leads with the metric that moved most and leaves out anything that stayed flat.
- Posts it straight to your leadership Slack channel, so nobody has to open a dashboard to find out how the business did yesterday.
What do I need to use this?
- A Looker account with permission to run the reports you want included. A Looker admin can set this up.
- Saved Looker reports covering the metrics you care about, such as revenue, new signups, and support volume, named clearly enough to find.
- A Slack workspace and a channel where your leadership team already reads updates.
How can I customize it?
- Change the timing: move it to 7am, or run it only on Monday for a weekly roll-up instead.
- Swap in the metrics that matter to your business, such as churn, pipeline created, or weekly active users.
- Adjust what counts as flat, so more or fewer metrics survive the filter and make it into the post.
- Send it to a different channel, or as a direct message to a single executive.
FAQs
Do I need to build new reports in Looker for this?
What happens to a metric that did not really change?
Will it still post if one of my reports fails to run?
Can I include more than three metrics?
Does this replace our dashboards?
Related templates
When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.
Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.
Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.
Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.
Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.
When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.
Stop hunting through dashboards every morning.
Get the numbers that moved, written in plain English, before your first meeting of the day.