Enterprise workflows
Workflows your team can run, save and re-run across 14 platforms
A workflow is the job you run by hand every week, written once and given a name. PaidSync saves it as TypeScript that composes 460+ tools across 14 platforms behind one endpoint, https://mcp.paidsync.ai/mcp, and runs it from a chat, on a schedule, or from your own agent. Every write inside a workflow is held for your approval before it touches an account. Five ship ready to run today. The rest are built around how your team already works.
The library
Twelve jobs a paid media team runs by hand every week.
Each one names the tools it calls, the platforms it genuinely covers, and the point where a human decides. Where a platform cannot do something, the card says so rather than implying it can.
Wasted spend sweep across a manager account
A ranked list of campaigns, ad groups and keywords burning budget at zero or poor conversions, per account, with the dollar figure attached.
Daily, or on demand
Google Ads, Meta Ads, Microsoft Ads, and every other connected platform
get_wasted_spend_report, get_search_terms_report, get_keyword_performance
One card per account listing the spend with no return, ranked by money. Nothing is paused until you approve the card.
Weekly cross-platform report
One table your finance team can sign off on: spend, clicks, conversions and return by platform and by brand, plus paid against organic from Search Console.
Every Monday
All 14 platforms in one pass
get_campaign_performance, get_account_summary, run_ga4_report, get_gsc_search_analytics
None. This workflow only reads.
Creative fatigue watch
The creatives whose frequency is climbing while click-through falls, before the drop reaches your return.
Daily
Meta Ads and TikTok Ads
get_ad_performance, get_campaign_performance
A refresh proposal per ad set. Creative changes are always an approval card, in every band.
Budget pacing check
Campaigns trending to over or under spend their period budget, with the adjustment that brings them back.
Daily
Google, Meta, LinkedIn, TikTok, Microsoft, Snapchat, Reddit, Pinterest and X
get_campaign_performance, get_account_summary
A budget adjustment card per campaign, held against the monthly ceiling you set.
Tracking integrity audit
Key events that stopped firing, tags without triggers, and the measurement gaps that quietly distort every bid.
Weekly
Google Analytics 4 and Google Tag Manager
run_ga4_report, get_ga4_metadata, list_gtm_tags, list_gtm_triggers
Any tag or event change is a card. The audit itself only reads.
Merchant Center disapproval sweep
Disapproved products and feed errors that are silently suppressing your Shopping reach, with the fix per product.
Daily
Google Merchant Center
merchant_list_data_sources, merchant_insert_product
Every product write is a card, and a delete additionally needs an explicit destructive confirmation.
Negative keyword build
Recurring search terms that spend and never convert, ranked by spend and ready to add as negatives.
Weekly
Google Ads and Microsoft Ads
get_search_terms_report, negative-keyword-candidates
The list is proposed as one card. Nothing is added to an account until you approve it.
Return drop diagnosis
Why return fell, separated into tracking loss, auction shift and creative fatigue, with the evidence for each.
On demand, or when a threshold trips
Google Ads and Meta Ads
get_campaign_performance, get_keyword_performance, get_search_terms_report, list_bidding_strategies
Three to five cards, each with the expected effect stated before you approve.
LinkedIn lead form audit
Lead forms with falling completion, campaigns paying for impressions with no leads, and the targeting that changed underneath.
Weekly
LinkedIn Ads
get_campaign_performance, get_ad_performance
Form and campaign changes are cards.
Portfolio audit across every client
A per client health score with the three highest-value fixes for each, so a lead can triage twenty accounts in one sitting.
Weekly
Every connected platform, every brand in the workspace
run_account_audit, account-audit, get_account_summary
One digest, no writes.
Conversion tracking setup chain
A tracking chain built end to end in one conversation, verified rather than assumed.
On demand
Google Tag Manager, Google Analytics 4 and Google Ads together
setup_google_ads_conversion, setup_ga4_event, setup_form_tracking
Each step is a card, and the workflow reads the tag back after it publishes to confirm it fires.
Scheduled account audit
The same audit your strategist would run, on a schedule, with findings ranked by dollar impact.
Weekly, per brand
Google Ads today, with the read layer on all 14
run_account_audit, account-audit
None. The auditor reports and never acts.
How a custom workflow is built for you
You keep the playbook. We remove the typing.
We watch the job once, write it as a saved workflow against your own accounts, and put the approval points where your team wants them. It starts read only, and you widen it per agent when the numbers say so. That sequence is the same four band engagement described in how an engagement works, and the controls behind it are listed on the security and controls page.
Workflows run in a sandbox with no network and no file access, batched so fifty calls finish in about a second rather than eight. A scheduled run gets a longer window than an interactive one. Nothing about the approval model changes when nobody is watching.
Frequently asked questions
What is a saved workflow?
A named piece of TypeScript that composes PaidSync tools into one repeatable job. You save it once with paidsync_workflows_save and run it by name with paidsync_workflows_run, from a chat, on a schedule, or from your own agent. It runs in a sandbox with no network and no file access, and every write inside it is held for approval exactly as it would be in a conversation.
Can we run these without building anything?
Yes. Five workflows ship with PaidSync and run today on a connected account: account-audit, find-waste, pause-zero-conv-keywords, weekend-underspend and negative-keyword-candidates. The pause workflow returns a preview by default and only applies when you set apply to true, which still goes through the destructive confirmation gate.
Which platforms can a workflow actually change?
Google, Meta, LinkedIn and OpenAI Ads support full campaign building. TikTok, Snapchat, Reddit, Pinterest, Microsoft and X are manage and optimise, so a workflow changes budget, status, targeting and bids on campaigns that already exist and you build new campaigns in the platform. Google Analytics 4, Tag Manager and Merchant Center write configuration and product data rather than campaigns. Search Console is read only.
What stops a workflow from spending money we did not approve?
Every write is proposed as a card before it runs, in every band except the ones you deliberately widen per agent. Mutating tools accept a dry run for a no-op preview, destructive operations need an explicit confirmation flag, and the workflow reads the change back after it applies so the result is checked against the proposal rather than assumed. Spend ceilings are enforced on our servers, not in the client.
How do we get a workflow built for our playbook?
Book a call. We map the job you run by hand today, write it as a saved workflow against your accounts, and hand it over with the approval points where your team wants them. You keep the strategic logic; the workflow removes the typing.
Can our own agents call these?
Yes. The workflows live behind the same endpoint as every other tool, https://mcp.paidsync.ai/mcp, with OAuth 2.0 sign-in. Anything that speaks the Model Context Protocol can list them and run them, including Claude, Claude Code, ChatGPT, Gemini, Copilot Studio and your own code.
Do workflows run when nobody is watching?
They can run on a schedule, and a scheduled run gets a longer execution window than an interactive one. It is scheduled checks rather than a live operator, and the approval model does not change: a scheduled run that wants to write still produces a card for a person.