CONTENT CREATION
Update setup docs when env vars or config schema change
When a commit touches environment variables or config schema files, the agent checks whether the setup and configuration docs still list them correctly and opens a doc PR for any…
How it runs
The automated pipeline, trigger to output.
- TriggerPush to default branchGitHub
- LogicFilter to env/config/schema changes only
- ActionExtract current config keys and descriptionsGitHub
- LogicDiff keys against documented ones
- ActionRewrite affected setup doc sections
- OutputOpen config-doc update pull requestGitHub
What it does
Watches commits to your main branch for changes to env files, config schemas, and settings examples. It diffs the declared configuration keys against what the setup documentation describes, then drafts a documentation update covering every added, removed, or renamed key.
When to use it
Use it when new contributors hit broken setups because the env or config docs lag behind the actual required variables. Especially useful for projects with a sprawling `.env.example` or a config schema that changes often.
How it works
- 1A push to the default branch fires the trigger.
- 2A filter step passes only commits that touch env files, config schemas, or settings examples.
- 3The agent extracts the full current set of config keys and their descriptions.
- 4It compares that set against the keys documented in the setup pages.
- 5A decision step categorizes each key as added, removed, renamed, or unchanged.
- 6It rewrites the affected setup sections to match the real schema.
- 7It opens a documentation pull request listing every key change.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.