# 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.

- Workflow type: agent
- Services: Looker, Slack Bot
- Categories: Operations
- Published: 2026-08-07

## What it does

- 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 you'll need

- 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.

## Prompt

Every 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.

## How to customize

- 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.

## FAQ

### Do I need to build new reports in Looker for this?

No. It runs the saved Looks you already have. The main thing that helps is naming them clearly, so the right report gets picked up for each metric.

### What happens to a metric that did not really change?

It gets left out. The snapshot only carries metrics that actually moved, which is what keeps it short enough for people to read every morning.

### Will it still post if one of my reports fails to run?

Yes. It posts the metrics it did get and adds a line naming the one that is missing, so a silent failure never looks like a quiet day.

### Can I include more than three metrics?

Yes. You can point it at as many saved reports as you like, though the snapshot stays deliberately short, so the least interesting numbers get filtered out first.

### Does this replace our dashboards?

No. It is a morning summary that tells leadership what moved and what to look at. The dashboards are still there when someone wants the full detail.

Use this prompt in General Input: https://www.generalinput.com/prompts/weekday-executive-kpi-snapshot-from-looker-into-slack