CONTENT CREATION
Keep ReadMe API reference in sync with code releases
On each tagged release the agent diffs your API surface against your ReadMe docs and, when endpoints or parameters changed, pushes updated reference pages and posts the summary…
How it runs
The automated pipeline, trigger to output.
- TriggerNew release taggedGitHub
- ActionFetch release diff and API changesGitHub
- ActionPull matching ReadMe reference pagesReadMe
- LogicGate: did any endpoint or field change?
- ActionUpdate affected ReadMe pages and examplesReadMe
- OutputPost updated-pages summary to SlackSlack
What it does
Triggers on a new tagged release, inspects what changed in your API code, and reconciles it against the published API reference in ReadMe. When endpoints, request fields, or response shapes have shifted, it updates the matching ReadMe pages and tells your team what moved.
When to use it
Use it when you ship an external API documented in ReadMe and your reference pages quietly fall behind each release. Ideal for developer-platform teams who treat the docs site as a product and cannot afford wrong examples.
How it works
- 1A new GitHub release tag fires the trigger.
- 2The agent fetches the release diff and identifies API-surface changes.
- 3It pulls the current matching pages from ReadMe.
- 4A decision step gates on whether any documented endpoint or field actually changed.
- 5For real changes it rewrites the affected ReadMe reference pages, including request and response examples.
- 6It publishes the updated pages to ReadMe.
- 7It posts a Slack summary of every page touched so docs owners can verify.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ReadMeAPI docs, changelog, auth.
- 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 Content Creation workflows
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Research-driven localized hero banners tuned per market
An agent researches cultural and seasonal cues for each target market, adapts the master hero concept to fit local context, generates a tailored image per locale.
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.