Flag the campaigns that stopped working
A 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.
Google Ads
4 steps1 integrationRuns on demand
Wasted spend is noticed a month late. What it costs while the work is still done by hand.
- 01Underperformance is only visible in comparison.
- 02Nobody wants to be the one who pauses a campaign.
- 03Spend continues while the decision is deferred.
- Pull spend14 campaigns · 30 days
- Find laggards3 below threshold
- Draft actionspause 2 · cut budget on 1
- Apply changeapproved · 2 paused
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Pull performance against the thresholds you set.Google Ads
- 02Isolate the campaigns that fell below them.ModuleX
- 03Draft the recommendation for each, with the numbers attached.ModuleX
- 04Review and approve before any campaign is changed.Google Ads
The workflow is an editable graph. Reading runs freely; review and approve before any campaign is changed waits for your opt-in approval until you loosen it. The graph is the receipt.
The ones to act on. Paste this into ModuleX chat, or hit Use this workflow.
flag the campaigns that stopped working: pull performance against the thresholds you set; isolate the campaigns that fell below them; draft the recommendation for each, with the numbers attached; review and approve before any campaign is changed. 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.
Flag the campaigns that stopped working. A short list of campaigns to act on, each with the numbers that put it there, and your approval in front of the change.
- google ads · create_campaign_report
A short list of campaigns to act on, each with the numbers that put it there, and your approval in front of the change.
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.
No. Changing a campaign waits for your approval.