DEVOPS
Open a GitLab issue when Vercel flags drift from source
On schedule, finds Vercel Edge Config flags that no longer match GitLab's flags.json and opens (or updates) a labeled GitLab issue documenting each drift for triage.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch live Edge Config from VercelVercel
- ActionFetch flags.json from GitLabGitLab
- LogicCompute drift set; exit if empty
- ActionFind existing open flag-drift issueGitLab
- OutputCreate or update GitLab drift issueGitLab
What it does
Turns flag drift into tracked work instead of a Slack message that scrolls away. Each run it diffs the live Vercel Edge Config against the committed `flags.json`, and for any divergence it opens a GitLab issue (or updates the existing open one) with a checklist of drifted flags, their live values, and expected values, tagged with a `flag-drift` label.
When to use it
Use it when drift needs an owner and an audit trail rather than an instant revert. Good for teams that reconcile flags during a weekly review and want each occurrence captured as a triageable, assignable issue.
How it works
- 1A schedule fires the reconciler (default daily).
- 2Fetch the live Edge Config map from Vercel and `flags.json` from GitLab.
- 3A logic step computes the drift set and exits quietly if empty.
- 4Search GitLab for an existing open `flag-drift` issue.
- 5Create a new issue or update the existing one with the current drift checklist and a link to the affected store.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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 DevOps workflows
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.