Weekly Census sync activity report for leadership
Every Monday morning, walk every Census sync and post a leadership-ready recap of what reached your CRMs and marketing tools this week.
Census
Google Sheets
Slack BotOperationsAI ReportsEvery Monday at 9am, produce a weekly reverse-ETL activation report for the leadership team.
Start by calling Census List Syncs to get every sync configured in the workspace, paginating through all pages. Also call Census List Destinations once and build a lookup from destination_id to destination name (Salesforce, HubSpot, Iterable, and so on) so the sheet and the Slack recap use human-readable destination names rather than numeric IDs.
For each sync, call Census List Sync Runs and keep only the runs whose start time falls in the last 7 days. From those runs compute: total runs, success rate (successful runs divided by total runs), total records synced (sum of updated plus inserted records), total rejected records, average runtime, and the single most common failure reason across the failed runs. If a sync had no runs in the last 7 days, keep it in the report with zeros so the sheet stays complete.
Append one row per sync to the "Census Weekly Activity" Google Sheet using Append Values. Columns, in order: week ending (today's date), sync name, destination (human name), total runs, success rate, records synced, rejected records, average runtime, top error. Preserve this column order across weeks.
Before writing the narrative, read prior weeks' rows already present in the sheet so you can compare this week to last week per destination. Then write a short executive summary aimed at non-technical leadership: how many total records reached CRMs and marketing tools this week, which destinations trended up or down versus last week, and the two or three syncs most in need of attention right now (paused syncs, syncs whose rejection rate spiked, or syncs whose success rate dropped). Keep it to a short paragraph followed by a small bullet list — leadership will not read the whole sheet.
Post that summary to the #data-leadership Slack channel using Slack Bot Send a Message, and include a link to the "Census Weekly Activity" Google Sheet at the bottom so anyone who wants the underlying detail can click through.
Additional information
What does this prompt do?
- Runs every Monday morning and pulls the last 7 days of activity for every Census sync in your workspace.
- Appends one row per sync to a Google Sheet with records synced, rejections, average runtime, and the top error, using human destination names.
- Compares this week to prior weeks already in the sheet and calls out which destinations trended up or down.
- Posts a short recap to your data leadership Slack channel with the two or three syncs most in need of attention and a link to the full sheet.
What do I need to use this?
- A Census workspace with active syncs (a workspace API key generated from Workspace Settings)
- A Google Sheet where the weekly rows will land (a fresh tab called 'Census Weekly Activity' works well)
- A Slack workspace with a channel for the recap (default: #data-leadership)
How can I customize it?
- Change the schedule to run Friday afternoons if you'd rather recap the week that just ended.
- Point the recap at a different Slack channel, or send a DM to the data lead in addition to the channel.
- Rename the sheet columns or add ones your team already tracks (for example, match rate or freshness), and the report will keep them in sync.
Frequently asked questions
Does this work now that Census is part of Fivetran?
Will running the report affect our syncs?
What if a sync had no runs in the past week?
Where does the up/down trend come from?
Can we send the recap to more than one Slack channel?
Related templates
Give leadership a clear read on data activation every Monday.
Set the recap up once and let your reverse-ETL activity tell its own story week over week.