DEVOPS
Refresh production synthetic budget baselines nightly
Runs nightly against the live production Vercel deployment, captures current synthetic metrics.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionFetch current production deployment URL from VercelVercel
- ActionRun synthetic checks against productionVercel
- LogicCompute new budget thresholds with tolerance margin
- ActionUpsert baseline thresholds into PostgresPostgres
- OutputPost refreshed baseline summary to SlackSlack
What it does
On a nightly schedule, this workflow measures the live production deployment with the same synthetic checks your promote gate uses, then stores the results (performance score, LCP, p95 latency, transfer size) as the new baseline budget in Postgres. This keeps your gate honest as the app legitimately evolves, so you compare new previews against where production actually is rather than a stale hardcoded number.
When to use it
Use it alongside any promote-blocking gate. Without a refreshing baseline, budgets either drift too loose or reject every deploy after a planned change. Run it nightly or after each successful production release.
How it works
- 1A nightly schedule triggers the workflow.
- 2The current production deployment URL is fetched from the Vercel API.
- 3The synthetic check suite runs against production and collects the metrics.
- 4A logic step computes the new budget thresholds, applying your tolerance margin.
- 5The thresholds are upserted into the Postgres baseline table keyed by environment.
- 6A short summary of the refreshed baseline is posted to Slack for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.