Facebook Ads to Google Sheets, reports stay current
Exporting Facebook Ads data “one more time” sounds harmless until you’re fixing column mismatches, chasing missing campaigns, and second-guessing what day the numbers actually reflect.
This Facebook Sheets sync hits performance marketers first. But client-facing agency owners and busy operators feel it too, because reporting is where small errors turn into big arguments. This workflow keeps one Google Sheet current, daily, without the recurring spreadsheet cleanup.
Below, you’ll see exactly what the automation does, what you’ll need, and how to think about setup so your reports stay reliable even as campaigns scale.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Facebook Ads to Google Sheets, reports stay current
flowchart LR
subgraph sg0["Set Schedule1 Flow"]
direction LR
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge"]
n2@{ icon: "mdi:cog", form: "rounded", label: "Aggregate", pos: "b", h: 48 }
n3@{ icon: "mdi:database", form: "rounded", label: "Update row in sheet4", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Checking if Campaign have data", pos: "b", h: 48 }
n7@{ icon: "mdi:database", form: "rounded", label: "Update Campaign statistics", pos: "b", h: 48 }
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get Campaign statistics"]
n9["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Checking Conversion"]
n10@{ icon: "mdi:database", form: "rounded", label: "Get Campaign ID", pos: "b", h: 48 }
n14@{ icon: "mdi:play-circle", form: "rounded", label: "Set Schedule1", pos: "b", h: 48 }
n1 --> n2
n2 --> n7
n14 --> n10
n10 --> n8
n10 --> n1
n9 --> n1
n3 --> n10
n8 --> n6
n7 --> n10
n6 --> n3
n6 --> n9
end
subgraph sg1["Set Schedule Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Code1"]
n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Get Only Active Campaign", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get Campaign from AD Account"]
n11["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/facebook.svg' width='40' height='40' /></div><br/>Add credentials to the Faceb.."]
n12@{ icon: "mdi:database", form: "rounded", label: "Add your campaign to file", pos: "b", h: 48 }
n13@{ icon: "mdi:play-circle", form: "rounded", label: "Set Schedule", pos: "b", h: 48 }
n0 --> n4
n13 --> n11
n4 --> n12
n5 --> n0
n11 --> n5
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n14,n13 trigger
class n6,n4 decision
class n3,n7,n10,n12 database
class n8,n5,n11 api
class n9,n0 code
classDef customIcon fill:none,stroke:none
class n1,n8,n9,n0,n5,n11 customIcon
The Problem: Facebook Ads reporting becomes a weekly fire drill
Facebook Ads data is deceptively hard to “just export.” One day you pull campaign stats, the next day the export format shifts, a campaign disappears because it paused, or someone filters the wrong date range and your report quietly lies. Then comes the manual cleanup: renaming headers, re-ordering columns, and copy-pasting into a master sheet that multiple people are editing at once. It’s not only time. It’s mental overhead, because you’re never fully sure the numbers are current until you re-check them.
The friction compounds. Here’s where it typically breaks down.
- Manual exports eat about 30 minutes per reporting cycle, and that’s before you fix formatting.
- Paused or ended campaigns get missed, which means your “totals” don’t match Ads Manager.
- Copy-paste mistakes sneak in, especially when multiple ad accounts or date ranges are involved.
- Client or leadership questions turn into a scavenger hunt across tabs, screenshots, and stale CSV files.
The Solution: Daily Facebook Ads metrics synced into Google Sheets
This n8n workflow pulls your Facebook Ads campaign data from the Facebook Graph API on a schedule, validates it, and writes it into a Google Sheet with the exact columns you expect. It doesn’t rely on someone remembering to export. It also doesn’t dump “raw chaos” into a spreadsheet and call it reporting. The workflow fetches campaigns, filters for active ones when needed, retrieves the latest metrics, and then updates or appends rows so the sheet stays current over time. If something looks off (like missing campaign stats or conversions that don’t parse), it routes through checks before your sheet gets updated.
The workflow starts with scheduled triggers that kick off API access and metric retrieval. Then it merges and summarizes records so you get clean, consistent rows. Finally, it writes campaign metrics into Google Sheets and updates existing entries so you don’t end up with duplicates and “mystery totals.”
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you manage 12 campaigns and you export performance every weekday. Even if export + cleanup takes only about 20 minutes a day, that’s roughly 1.5 hours a week gone, and it rarely stays that low. With this workflow, you spend about 30 minutes once to set the sheet headers and connect credentials, then the daily run is hands-off. You might check the sheet for a minute or two, but you’re no longer rebuilding the report each time.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Facebook Graph API to pull campaign and metric data.
- Google Sheets to store and share the reporting table.
- Facebook access token + ads_read permission (get it from your Facebook App in Meta for Developers).
Skill level: Intermediate. You’ll connect accounts, set a sheet schema, and paste API credentials carefully.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Daily scheduled run. Two schedule triggers kick things off: one initiates Facebook Graph API access, and another pulls the campaign IDs already tracked in your sheet.
Campaign discovery and filtering. The workflow fetches the ad account’s campaigns, then filters for active campaigns when that’s the reporting view you want. This is where you avoid clutter from old tests while still keeping the option to track everything.
Metric retrieval and cleanup. Using the campaign IDs, it pulls key stats like impressions, clicks, CPC, CTR, conversions, and spend. It also runs validation and conversion checks, which helps catch partial API responses or weirdly formatted fields before anything gets written.
Sheet write-back. Cleaned records are merged, summarized, and then written into Google Sheets, updating existing rows and appending new campaigns as they appear. Your spreadsheet becomes the source of truth for reporting and sharing.
You can easily modify the date range (“From” and “To”) to match your reporting cadence, like last 7 days or month-to-date, based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set the automated run schedule for both reporting streams so the workflow starts on time.
- Open Scheduled Trigger A and define the schedule you want for fetching ad account campaigns.
- Open Scheduled Trigger B and define the schedule for pulling campaign IDs and metrics.
- Confirm both triggers are enabled and connected to their downstream nodes.
Step 2: Connect Facebook Graph API Access
Authenticate and prepare the Facebook Graph API connection used to retrieve campaigns.
- Open Configure Graph API Access and connect your Facebook Graph API credentials.
- Credential Required: Connect your facebookGraphApi credentials.
- Verify that Configure Graph API Access outputs to Fetch Ad Account Campaigns.
Step 3: Set Up Campaign Data Processing
Prepare the logic that filters and validates campaigns and verifies conversions.
- In Fetch Ad Account Campaigns, confirm it receives input from Configure Graph API Access.
- Open Script Processor to implement any transformations or parsing required before filtering.
- Configure Filter Active Campaigns to route only active campaigns into the output flow.
- Open Retrieve Campaign Metrics and confirm it receives campaign IDs from Retrieve Campaign IDs.
- Configure Validate Campaign Data to check the metric payload, then route valid data to Modify Sheet Row and invalid or flagged data to Verify Conversions.
Step 4: Connect Google Sheets
Authorize all Sheets nodes that read or write campaign IDs and metrics.
- Open Retrieve Campaign IDs and connect Google Sheets credentials.
- Credential Required: Connect your googleSheets credentials to Retrieve Campaign IDs, Modify Sheet Row, Write Campaign Metrics, and Append Campaign to File.
- Ensure Modify Sheet Row receives input from Validate Campaign Data and outputs back to Retrieve Campaign IDs for the loop.
- Confirm Write Campaign Metrics is connected after Summarize Records to log the final metrics.
Step 5: Configure the Parallel Metrics Stream
Set up the parallel branch that merges campaign IDs and conversion checks to summarize results.
- Confirm Retrieve Campaign IDs outputs to both Retrieve Campaign Metrics and Combine Streams in parallel.
- Ensure Verify Conversions outputs into Combine Streams so conversion verification is merged with the campaign ID stream.
- Open Summarize Records and verify it aggregates the merged output before writing to Write Campaign Metrics.
Step 6: Configure Output and Logging
Finalize where active campaigns and summarized metrics are stored.
- Open Append Campaign to File and confirm it receives only active campaigns from Filter Active Campaigns.
- Verify Write Campaign Metrics writes aggregated results after Summarize Records.
Step 7: Test and Activate Your Workflow
Validate that each branch runs end-to-end before enabling the schedule.
- Click Execute Workflow to run a manual test from Scheduled Trigger A and Scheduled Trigger B.
- Check that Append Campaign to File and Write Campaign Metrics both receive data and write rows in Google Sheets.
- Verify the parallel branch completes by checking that Summarize Records outputs aggregated results.
- When successful, toggle the workflow to Active for scheduled execution.
Common Gotchas
- Facebook Graph API credentials can expire or need specific permissions. If things break, check your access token status in Meta for Developers (and confirm ads_read) first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 45 minutes if you already have your Facebook App and Google Sheet ready.
No. You will mostly copy credentials, connect accounts, and match the sheet headers.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Facebook API usage (usually negligible for daily pulls) and any optional OpenAI usage if you keep the AI nodes enabled.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s one of the simplest tweaks. Change the Scheduled Trigger timing to weekly, then adjust the “From” and “To” fields the workflow writes into your sheet so they reflect your weekly window. Many teams also add a second tab for “weekly snapshots” while keeping the daily tab as the raw, always-current log.
Most of the time it’s an expired access token or missing ads_read permission on your Facebook App. Regenerate the token in Meta for Developers, then update the credential inside n8n and re-run the workflow. It can also fail when the ad account ID is wrong, the app isn’t allowed to access that ad account, or you hit rate limits while pulling a lot of campaigns at once. If the workflow worked yesterday and fails today, token expiry is honestly the first thing to check.
Plenty for most small teams: dozens to a few hundred campaigns is normal for a daily pull, as long as your API permissions are correct and your n8n instance has reasonable resources.
It depends on how “clean” you want the final sheet to be. Zapier and Make can move data, but Facebook Ads reporting often needs branching logic, validation, merging, and updates to existing rows, which n8n handles comfortably without turning into a fragile chain of steps. n8n also gives you a self-hosted option, which can be a big deal when you’re running daily workflows at scale. On the flip side, if your requirement is just “send one metric to one sheet,” Zapier or Make might be faster to set up. Talk to an automation expert if you want a quick recommendation for your exact setup.
Once this is running, your reporting sheet updates itself and the numbers stop being a debate. Set it up, spot-check it, then get back to optimizing campaigns instead of exporting them.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
