A report should tell you what happened, not what you hope happened.
Scheduled reports should be honest. This demo shows the weekly, monthly, anomaly and skip branches — every metric labelled with its source so you can audit the number, not just the slide.
What triggers this workflow
Cron-style trigger fires the report at the agreed time.
Source: Schedule (cron)
Workflow steps
- Twenty CRM + n8nPull dataRead the agreed metrics from Twenty CRM, the calendar and ad accounts.
- n8n + LLM stepComposePlain-English summary with metric labels and source links.
- n8nBranchWeekly / monthly / anomaly / skip — different cadence and audience.
- Listmonk + ChatwootSendEmail the report; anomaly alerts go to the operations lead as a private note.
Tools used
Human handoff
Anomaly alerts always reach a person
An anomaly in the report (response time spike, pipeline drop, conversion crash) triggers a private alert to the operations lead with the underlying data attached.
- Lead-response median jumps by 3x in a single day
- Pipeline drops more than 30% week on week
- Ad spend exceeds the daily cap
Try it in your browser
Edit the sample inputs, choose a branch, and see what the workflow produces. The sandbox runs offline — no accounts touched, no messages sent.
Try it in your browser
Edit the inputs, pick a branch, and see what the workflow produces. Runs entirely in your browser — no messages are sent, no accounts are touched.
1. Trigger
Scheduled week report — focus area: lead response time.
2. Branch handling
Subject: Week growth snapshot This week's snapshot: • New enquiries (configurable count): 12 • Median first-response time: 11 min • Bookings from AI-led conversations: 4 • Reviews collected (same neutral link): 7 • Outstanding quotes older than 5 days: 2 Full breakdown attached. — LetsGrowMate automated report
Numbers shown are illustrative. Production numbers come from your Twenty CRM + connected integrations.
Sample data only. Numbers, names and messages are placeholders for illustration. Wire the live workflow separately using the setup notes below.
n8n workflow template
n8n template — LGM 05 Scheduled Reporting (SIMULATED, inactive). Ships with active: false — no live integrations are wired. See the setup section below for the wiring checklist, and download the JSON to inspect or import it.
Setup for production
Wiring it for production
Live deployment needs data sources, metric definitions and an anomaly threshold.
- Connect the data sources (Twenty CRM, calendar, ad accounts).
- Define each metric with a clear label and source — no orphan numbers.
- Set the anomaly thresholds and the operations lead as the recipient.
- Document the cadence and review it quarterly.
Production prerequisites
- Data sources available with read-only access
- Metric definitions signed off — every number has a source
- Operations lead named as the anomaly recipient
Nothing here runs by default. Configuration has to be in place before any live send, booking or contact write.
Questions
Could the report invent a metric?
No. Every metric is labelled with its source and pulled directly from the connected data. If a source is missing, the report flags it rather than estimating.
What about attribution limits?
The report carries an attribution-limits section so the reader knows which numbers are observed vs attributed vs estimated.
More demos you can run in your browser
Scheduled Reporting across the platform
Want this scheduled reporting workflow running on your stack?
Pick the demo you're curious about or describe your own. We'll come back with what a real deployment looks like for your business — the workflow, the prerequisites, the people involved.