ENGINEERING
Weekly review cycle-time report from Postgres to Notion
Once a week it reads the accumulated daily latency snapshots from Postgres, computes median and p90 review cycle times plus week-over-week trend.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers the report run
- ActionQuery last two weeks of latency snapshotsPostgres
- LogicCompute median, p90, and week-over-week deltas
- OutputPublish a dated cycle-time report page to NotionNotion
What it does
Turns the raw daily latency snapshots your tracker collects into a readable weekly report. It calculates median and p90 review wait times, compares them to the prior week, flags which reviewers improved or regressed, and writes a clean Notion page leadership can skim.
When to use it
When you already log per-PR latency snapshots (for example via the daily leaderboard workflow) and want a durable weekly artifact for retros, staffing decisions, or process reviews — without anyone hand-building a spreadsheet.
How it works
- 1A weekly schedule triggers the report run.
- 2The flow queries Postgres for the last week (and prior week) of latency snapshots.
- 3A logic step computes median, p90, and week-over-week deltas per team and reviewer.
- 4It assembles a structured report with trend callouts and the worst-affected PRs.
- 5It creates a dated Notion page under your engineering reports space with the summary and tables.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect NotionPages, databases, comments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.