DEVOPS
Escalate Stalled Trello Release Cards Against GitLab MR Activity
Runs on a schedule to find release cards stuck in-progress whose linked GitLab MRs have had no commits or comments for too long, then flags the card and alerts the owner in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule sweep
- ActionList in-progress cards from Trello boardTrello
- ActionRead last commit and comment time of linked GitLab MRsGitLab
- LogicIs MR activity older than staleness window?
- ActionApply "Stalled" label to the Trello cardTrello
- OutputSend Slack alert to the card ownerSlack
What it does
On a daily schedule, this scans the in-progress lists of your release-train board and cross-checks each card's linked GitLab merge requests for recent activity. Cards whose MRs have been silent past a staleness threshold get a red "Stalled" label and the card owner is pinged in Slack with the specifics.
When to use it
Use it when release cards drift for days because an MR is blocked, abandoned, or waiting on review and nobody notices until the release date slips. This gives you an early-warning sweep without anyone babysitting the board.
How it works
- 1A daily schedule trigger starts the sweep.
- 2All cards in the configured in-progress lists are pulled from Trello.
- 3For each card, the linked GitLab MRs are checked for their last commit and last comment timestamps.
- 4A logic step compares the most recent activity against the staleness window (default seven days).
- 5Stale cards get a "Stalled" label applied in Trello.
- 6A Slack direct alert is sent to each card's member listing the stuck MR and days idle as the output.
Set it up
What you configure once, before turning it on.
- 1Connect TrelloKanban boards for everything.
- 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.