Get an approved draft onto the docs site
An approved draft turned into a docs change, ready for the normal review that already exists. Built for a team where finished documentation waits days for someone to publish it.
Notion
GitHub
4 steps2 integrationsRuns on demand
Finished docs wait days for someone to publish. What it costs while the work is still done by hand.
- 01The draft is done but the publishing step needs a different person.
- 02Formatting is redone during the move.
- 03Docs drift behind the product because publishing is a chore.
- Read draftsearch · approved, 1,400 words
- Convertmdx · 3 headings, 2 snippets
- Reviewlinks, frontmatter · checked
- Open changedocs/quickstart · PR opened
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the approved draft.Notion
- 02Convert it into the structure the docs site expects.ModuleX
- 03Review the converted version.ModuleX
- 04Open the change on the docs repository.GitHub
The workflow is an editable graph. Reading runs freely; review the converted version waits for your opt-in approval until you loosen it. The graph is the receipt.
Drafted to a docs change. Paste this into ModuleX chat, or hit Use this workflow.
get an approved draft onto the docs site: read the approved draft; convert it into the structure the docs site expects; review the converted version; open the change on the docs repository. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Get an approved draft onto the docs site. An approved draft turned into a docs change, ready for the normal review that already exists.
- notion · search
- github · create_pull_request
An approved draft turned into a docs change, ready for the normal review that already exists.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Adapt one announcement for each channelOne announcement, rewritten per channel, reviewed in one place before anything goes out. Built for a one-person marketing team posting the same text everywhere.
See which posts are actually being readA digest that separates the pieces people found from the pieces they did not. Built for a content lead who publishes steadily and reviews performance rarely.
Fix what the SEO crawl actually foundA short ordered list of page-level fixes, each already written as a ticket. Built for a marketer holding a 200-row audit export and no idea which row matters.
About this use case.
It opens the change; your existing review and merge process still applies.