DEVOPS
Snapshot Vercel flag drift to BigQuery for compliance history
On schedule, records the full live-vs-source flag comparison as timestamped rows in BigQuery, building a queryable history of every flag's state and any drift events.
How it runs
The automated pipeline, trigger to output.
- Trigger15-minute schedule fires
- ActionFetch live Edge Config from VercelVercel
- ActionFetch flags.json source from GitLabGitLab
- LogicJoin by key, stamp drift status + timestamp
- OutputAppend rows to BigQuery flag-history tableBigQuery
What it does
Builds an immutable audit log of feature-flag state over time. Each run captures the live Vercel Edge Config values alongside the GitLab `flags.json` source values, computes per-flag drift status, and appends one timestamped row per flag to a BigQuery table. Over weeks this becomes a full history you can query for when a flag changed, how long it was drifted, and who diverged from source.
When to use it
Use it for compliance, incident forensics, or change-management reporting where you must prove the state of production flags at any past moment. Pairs well with a separate remediation workflow that fixes drift in real time.
How it works
- 1A schedule fires the snapshot job (default every 15 minutes).
- 2Fetch live Edge Config values from Vercel.
- 3Fetch the canonical `flags.json` from GitLab at the default branch.
- 4A logic step joins the two by key and stamps each flag with in-sync or drifted status plus the run timestamp.
- 5Append the rows to the BigQuery flag-history table for later querying.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect BigQueryDatasets, queries, schemas.
- 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.