DEVOPS
Push merged GitLab flag changes to Vercel Edge Config on MR merge
When a merge request touching flags.json merges in GitLab, applies the new flag values to the Vercel Edge Config store and confirms the apply in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge request merged webhookGitLab
- LogicFilter: MR changed flags.json on default branch
- ActionFetch merged flags.json at commit SHAGitLab
- ActionPatch Vercel Edge Config to matchVercel
- OutputConfirm applied changes in SlackSlack
What it does
Makes GitLab the write path for feature flags. The moment a merge request that modifies `flags.json` merges into the default branch, this workflow reads the merged file, patches the Vercel Edge Config store to match exactly, and confirms the applied changes in Slack so the team sees the rollout land.
When to use it
Use it once you've decided flags are code: every change goes through review and merge, never the Vercel dashboard. This closes the loop so an approved MR actually takes effect in production within seconds, no manual dashboard step.
How it works
- 1A GitLab merge webhook triggers on merge events targeting the default branch.
- 2A logic step filters to merges that actually changed `flags.json`, ignoring everything else.
- 3Fetch the merged `flags.json` content at the merge commit SHA from GitLab.
- 4Patch the Vercel Edge Config store with the new key/value set via the Vercel API.
- 5Post a Slack confirmation naming the MR, author, and the keys that changed.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect VercelDeploys, runtime logs, analytics.
- 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
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.