ENGINEERING
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch current OpenAPI specGitHub
- LogicFind deprecated paths + days to sunset
- LogicEscalate sunsets under 14 days to SlackSlack
- OutputEmail per-team sunset countdownGmail
What it does
Keeps deprecation promises from being forgotten. Each week it reads the API spec, finds every endpoint flagged `deprecated` with a `sunset` date, calculates days remaining, and emails the owning teams a personalized list of what they still call that is going away — escalating the urgent ones to Slack.
When to use it
You deprecate endpoints with a published sunset window and need steady, automatic nudges so consumers actually migrate before the cutoff instead of being broken on removal day.
How it works
- 1A weekly schedule triggers the flow.
- 2Fetch the current OpenAPI spec from GitHub.
- 3Extract every deprecated operation and its sunset date, computing days remaining.
- 4Map each deprecated path to consuming teams via the usage/ownership map.
- 5Branch: for any sunset under 14 days, post an urgent escalation to the team's Slack channel.
- 6Email each affected team its tailored sunset countdown via Gmail.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect GmailRead, draft, send, label.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.