DEVOPS
Announce Shipped Trello Release Cards to Slack with MR Summary
When a release card lands in the Done list, this gathers its merged GitLab MRs and posts a formatted ship-it announcement to Slack with author credits and the diff stat.
How it runs
The automated pipeline, trigger to output.
- TriggerTrello card moved to "Done / Shipped" listTrello
- ActionFetch referenced merge requests from GitLabGitLab
- LogicKeep only MRs that are actually merged
- LogicBuild digest with authors and diff stats
- OutputPost ship-it announcement to Slack channelSlack
What it does
Detects when a card on the release-train board is moved into the "Done / Shipped" list and turns it into a polished Slack announcement. It pulls the merge requests tied to the card from GitLab, tallies how many merged and by whom, and posts a celebratory ship-it message to your release channel.
When to use it
Use it when releases finish on the board but nobody outside the dev team hears about it until someone manually writes a Slack update. This automates the announcement and gives proper author credit every time.
How it works
- 1A Trello card entering the "Done / Shipped" list triggers the run.
- 2MR references are extracted from the card description.
- 3Each referenced GitLab MR is fetched to confirm merged status and collect author plus changed-files counts.
- 4A logic step filters out any MR that is not actually merged, so half-done cards do not announce prematurely.
- 5The surviving MRs are formatted into a digest with contributor mentions and a combined diff stat.
- 6The ship-it message is posted to the configured Slack channel as the final 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
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.