Write the launch recap while the numbers are fresh
A recap with the numbers attached, written while people still remember the week. Built for a team that finishes a launch and never writes down how it went.
Google Analytics
Google Ads
Notion
4 steps3 integrationsRuns on demand
The recap is written weeks later, if at all. What it costs while the work is still done by hand.
- 01The recap is written weeks later, if at all.
- 02The numbers come from four tools and one memory.
- 03The next launch repeats the same mistakes.
- Pull traffic18.4k sessions · 212 signups
- Pull campaigns6 campaigns · launch window
- Assemble recapwhat moved · what did not
- Publish notecreate_page · team notes
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Pull traffic and signups for the launch window.Google Analytics
- 02Pull the campaign and social activity for the same window.Google Ads
- 03Assemble a recap: what was done, what moved, what did not.ModuleX
- 04Publish it to the team's notes.Notion
The workflow is an editable graph. Reading runs freely; publish it to the team's notes waits for your opt-in approval until you loosen it. The graph is the receipt.
Recapped while it is fresh. Paste this into ModuleX chat, or hit Use this workflow.
write the launch recap while the numbers are fresh: pull traffic and signups for the launch window; pull the campaign and social activity for the same window; assemble a recap: what was done, what moved, what did not; publish it to the team's notes. 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.
Write the launch recap while the numbers are fresh. A recap with the numbers attached, written while people still remember the week.
- google analytics · run_report
- google ads · create_campaign_report
- notion · create_page
A recap with the numbers attached, written while people still remember the week.
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 reports what the tools recorded; the interpretation is the team's.