DEVOPS
Reconcile live Vercel Edge Config flags against GitLab source of truth
On a schedule, diffs the live Vercel Edge Config feature flags against the canonical flags.json committed in GitLab and posts any drift to Slack with a per-flag breakdown.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires
- ActionRead live Edge Config key/value mapVercel
- ActionFetch flags.json from GitLab default branchGitLab
- LogicDiff live vs. source, classify each flag
- LogicBranch: drift found vs. clean
- OutputPost drift report to Slack channelSlack
What it does
Keeps your runtime feature flags honest. Every run it pulls the active Vercel Edge Config store, pulls the canonical `flags.json` from the main branch of your GitLab config repo, computes a three-way diff (added live, missing live, value mismatch), and reports drift to your platform channel. If everything matches it stays silent or posts a quiet all-clear.
When to use it
Run it when manual dashboard edits or rushed hotfixes have a habit of leaving the live Edge Config out of sync with what's in version control. It turns "who flipped that flag in prod?" into a daily, auditable answer instead of a postmortem.
How it works
- 1A schedule fires the reconciler (default hourly).
- 2Fetch the current key/value map from the Vercel Edge Config store via the Vercel API.
- 3Fetch `flags.json` from GitLab at the default branch ref.
- 4A logic step computes the diff and classifies each flag as in-sync, drifted value, live-only, or repo-only.
- 5If any drift exists, post a formatted Slack message listing each offending flag, its live value, and its expected value; otherwise mark the run clean.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.