ENGINEERING
Publish a Figma rename changelog to Confluence and notify Teams
After a Code Connect mapping is updated for a renamed component, this records the old-to-new mapping in a Confluence changelog page and pings the affected squads in Microsoft…
How it runs
The automated pipeline, trigger to output.
- TriggerCode Connect mapping updatedFigma
- ActionRead new Code Connect map for name and sourceFigma
- LogicSkip non-breaking internal renames
- ActionAppend a row to the Confluence changelog pageConfluence
- OutputNotify affected squads in Microsoft TeamsMicrosoft Teams
What it does
Keeps a durable, searchable record of every design-system rename. When a Code Connect mapping changes, it appends a row to a Confluence changelog (old name, new name, source path, date, author) and posts a heads-up to the relevant Microsoft Teams channels so consumers update their usage.
When to use it
Use it in organizations where multiple product squads consume one design system and need an audit trail of component renames. It answers "when did Button/Primary become Button/Solid and where's the code?" without spelunking commit history.
How it works
- 1A Code Connect mapping update event triggers the flow.
- 2Read the new Code Connect map to capture the current `codeConnectName` and `codeConnectSrc`.
- 3Branch: skip purely internal renames tagged as non-breaking.
- 4Append a structured row to the Confluence changelog page.
- 5Post a notification with the before/after mapping to the affected Microsoft Teams channels.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.