DEVOPS
Tear down preview env when a GitLab MR merges or closes
Triggers on GitLab merge-request merge or close events and immediately deletes the matching Vercel preview deployment for that branch.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR merged or closedGitLab
- LogicExtract branch and confirm terminal state
- ActionFind Vercel preview for branchVercel
- ActionDelete matching preview environmentVercel
- OutputConfirm teardown in SlackSlack
What it does
This workflow ties preview-environment lifecycle directly to your GitLab merge requests. The instant an MR is merged or closed, it finds the Vercel preview deployment for that branch and tears it down, so finished or abandoned work stops consuming build and hosting budget.
When to use it
Use it when your team uses GitLab and wants preview environments cleaned up event-driven rather than on a daily sweep. It closes the gap between an MR being done and its preview being decommissioned, the window where stale previews quietly cost money.
How it works
- 1A GitLab webhook fires on merge-request merged or closed events.
- 2A logic step extracts the source branch name and confirms the event is a terminal state (merged or closed, not just updated).
- 3A Vercel action looks up preview deployments for that branch.
- 4A Vercel action deletes the matching preview environment.
- 5A Slack message confirms the teardown with the MR title, branch, and deployment removed.
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.