ENGINEERING
Sync source-map verification status to a release-health dashboard
On each Sentry release-created event, it records artifact counts, symbolication probe results.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry release-created webhookSentry
- ActionList artifacts and run symbolication probeSentry
- ActionLook up linked Vercel deployment by SHAVercel
- LogicCompute release-health verdict and reason
- ActionUpsert row into Airtable release-health tableAirtable
- OutputNotify channel when release is unhealthySlack
What it does
It builds a living record of source-map health across every release. Whenever Sentry registers a new release, it captures whether maps were uploaded, whether frames resolve, and which Vercel deploy it maps to, then writes a row to an Airtable dashboard the whole team can scan.
When to use it
Use it when you want visibility and trend data — not just alerts. Great for spotting which services or bundlers repeatedly ship without maps, and for proving release-health improvements over time.
How it works
- 1A Sentry release-created webhook fires with the release and version.
- 2The flow lists the release's artifacts and runs a symbolication probe in Sentry.
- 3It looks up the matching Vercel deployment by git SHA to link build metadata.
- 4A logic step computes a health verdict and reason from the gathered signals.
- 5It upserts a row into the Airtable release-health table with all fields.
- 6If the verdict is unhealthy, it posts a heads-up to Slack so someone follows up.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect AirtableBases, tables, views, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
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…
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.
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.
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.
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.
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.