ENGINEERING
Propagate Figma component renames into Code Connect and open a GitLab MR
When a Figma library component is renamed, this updates the matching Code Connect mappings and opens a GitLab merge request with the corrected source paths and component names…
How it runs
The automated pipeline, trigger to output.
- TriggerFigma library component renamed (publish event)Figma
- ActionRead existing Code Connect map for the nodeFigma
- LogicProceed only if component name changed
- ActionWrite corrected Code Connect mapping to FigmaFigma
- ActionOpen GitLab MR updating the Code Connect sourceGitLab
- OutputPost MR link to design-systems Slack channelSlack
What it does
Detects a renamed Figma library component, reads the existing Code Connect map for that node, rewrites the mapping to point at the renamed code component, and opens a GitLab merge request carrying the change so reviewers can approve the design-to-code relink in one place.
When to use it
Run this whenever a designer renames a component in a shared Figma library and the corresponding React/Vue component is renamed in the repo. It keeps `get_code_connect_map` accurate without a developer manually editing `.figma.tsx` files and chasing every reference.
How it works
- 1A Figma library publish event fires when a component is renamed.
- 2Read the current Code Connect map for the affected node to capture the old `codeConnectSrc` and `codeConnectName`.
- 3Branch: only proceed if the component name actually changed (skip cosmetic edits).
- 4Write the corrected Code Connect mapping back to Figma for the node.
- 5Open a GitLab merge request updating the Code Connect source file with the new name and path.
- 6Post the MR link to Slack so the design-systems team can review and merge.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 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 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.