DEVOPS
Backfill a New Trello Release Card with Open GitLab MRs by Label
When a new card is created in a release-planning list, this queries GitLab for open MRs carrying the matching release label and writes their titles, authors, and links…
How it runs
The automated pipeline, trigger to output.
- TriggerNew card created in a "Planning" listTrello
- LogicParse target release label from list or title
- ActionQuery GitLab for open MRs with that labelGitLab
- LogicAny matching MRs found?
- OutputWrite MR checklist into the Trello cardTrello
What it does
Watches the release-planning lists on your Trello board and, when a fresh card is created for an upcoming version, queries GitLab for every open merge request labeled for that release. It then writes those MRs into the card as a checklist of title, author, and link so the planning card arrives pre-filled.
When to use it
Use it when a release manager opens a card per upcoming version and otherwise has to manually hunt GitLab for which MRs are slated for it. This removes the copy-paste step and keeps the candidate list current from card creation.
How it works
- 1A new card created in a "Planning vX.Y" list triggers the run.
- 2The target release label is parsed from the list or card title.
- 3GitLab is queried for open MRs carrying that release label.
- 4A logic step skips the run cleanly if no matching MRs are found, leaving the card untouched.
- 5The matched MRs are formatted into a checklist of title, author, and URL.
- 6The checklist is written into the Trello card description as the output.
Set it up
What you configure once, before turning it on.
- 1Connect TrelloKanban boards for everything.
- 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
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.