Weekly Metrics Digest
Numbers that live in five dashboards get checked in none of them. This workflow gathers revenue, leads, tasks completed and pipeline value into a single weekly email with the previous week for comparison, so trends become visible before they become problems.
What you get
Workflow blueprint
The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.
Getting it into Zapier
Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 7 steps, so it is a copy-and-paste job rather than a design job.
You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →
Not on Zapier?
An n8n workflow JSON ships with this template. Import it and all 7 steps arrive on the canvas wired in order, and 6 of the 7 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node.
What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.
A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.
Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →
Setup steps
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Implementation notes
- Lead count and Proposal count need a source step you add — see the note on the Create Spreadsheet Row step. Everything else in this digest works out of the box.
- Start with four numbers. A digest with twenty metrics gets skimmed and then ignored.
- The Metrics sheet is what makes comparison possible — the Zap both writes to it and reads from it.
- Add Google Analytics, Plausible or your CRM as extra find steps once the basic digest is a habit.