n8n Ad Platforms Reporting Connectors
Budget: $10 – $30 USD
I’m putting together a set of five MCP-style connectors that will run inside n8n and feed Claude with daily ad-performance summaries. The connectors I need are for Facebook Ads, Google Ads, TikTok Ads, Snapchat Ads, and GA4. Their sole purpose is automated reporting; I’m not asking for full data-sync or live dashboards—just reliable, scheduled pulls of core performance metrics.
Here’s what I expect to receive:
• One n8n workflow (or sub-workflow) per platform that authenticates through the official API, fetches ad-performance metrics, formats the data, and posts it to Claude via the Claude API.
• A master workflow that triggers each connector on the chosen schedule (default: once every 24 h).
• Clear setup instructions, including any required API keys, scopes, and webhook URLs.
• Brief inline comments so I can tweak date ranges or metric lists later.
Acceptance criteria
1. Each connector fetches at least impressions, clicks, spend, and conversions for the previous day.
2. Workflows execute without errors in a fresh n8n install running the current LTS build.
3. Claude receives a JSON payload that matches the agreed schema and returns a 2xx status.
4. All code and instructions are delivered in a single Git repo or ZIP.
I’m happy to answer edge-case questions (e.g., handling multiple ad accounts or paginated API responses) as we go. If you’ve built similar n8n integrations before, let me know and include a quick example of your approach to token refresh.
Here’s what I expect to receive:
• One n8n workflow (or sub-workflow) per platform that authenticates through the official API, fetches ad-performance metrics, formats the data, and posts it to Claude via the Claude API.
• A master workflow that triggers each connector on the chosen schedule (default: once every 24 h).
• Clear setup instructions, including any required API keys, scopes, and webhook URLs.
• Brief inline comments so I can tweak date ranges or metric lists later.
Acceptance criteria
1. Each connector fetches at least impressions, clicks, spend, and conversions for the previous day.
2. Workflows execute without errors in a fresh n8n install running the current LTS build.
3. Claude receives a JSON payload that matches the agreed schema and returns a 2xx status.
4. All code and instructions are delivered in a single Git repo or ZIP.
I’m happy to answer edge-case questions (e.g., handling multiple ad accounts or paginated API responses) as we go. If you’ve built similar n8n integrations before, let me know and include a quick example of your approach to token refresh.
Related categories:
JSON
Documentation
Data Integration
API Development
API Integration
Google Ads
Facebook Ads
n8n