Adapt one announcement for each channel
One announcement, rewritten per channel, reviewed in one place before anything goes out. Built for a one-person marketing team posting the same text everywhere.
Notion
LinkedIn
4 steps2 integrationsRuns on demand
The same copy reads badly everywhere but one. What it costs while the work is still done by hand.
- 01The same copy reads badly on every channel but one.
- 02Rewriting it three times is the part that gets skipped.
- 03Posts go out inconsistently, or not at all.
- Read sourcesearch · 1 announcement
- Rewrite3 versions · per channel
- Review setside by side · approved
- Schedule postcreate_comment · queued 3
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the source announcement.Notion
- 02Rewrite it for each channel's format and length.ModuleX
- 03Review every version side by side.ModuleX
- 04Schedule or post them.LinkedIn
The workflow is an editable graph. Reading runs freely; review every version side by side waits for your opt-in approval until you loosen it. The graph is the receipt.
One message, each channel's voice. Paste this into ModuleX chat, or hit Use this workflow.
adapt one announcement for each channel: read the source announcement; rewrite it for each channel's format and length; review every version side by side; schedule or post them. 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.
Adapt one announcement for each channel. One announcement, rewritten per channel, reviewed in one place before anything goes out.
- notion · search
- linkedin · create_text_post_organization
One announcement, rewritten per channel, reviewed in one place before anything goes out.
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.
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.
Flag the campaigns that stopped workingA short list of campaigns to act on, each with the numbers that put it there, and your approval in front of the change. Built for a growth lead who notices wasted spend a month late.
About this use case.
Every version waits for your approval first.