adlaneSign in Daily and weekly reports
Read spend, clicks, impressions and attributed conversions for explicit date ranges in each account’s timezone, then deliver a formatted summary wherever your team reads it.
N8N INTEGRATION
Adlane + n8n
Automate Google and Meta ads reporting. Pull campaign performance from your connected accounts into n8n workflows and send it to Slack, email, Google Sheets or anywhere else your team works.
Install the nodeRead-only. No budget or ad changes.
WHAT YOU CAN AUTOMATE
Campaign evidence, on a schedule.
Alerts on changes
Compare yesterday with your own baseline and notify the right person when spend jumps, conversions drop or a campaign’s status changes.
Exports and client reporting
Append rows to a spreadsheet or database, or loop over every connected account to produce one report per client from a single credential.
SETUP GUIDE
From install to first report.
You need n8n Cloud or a self-hosted n8n instance, and an Adlane account with at least one connected Google Ads or Meta Ads account. The node calls the Adlane REST API directly; it does not use an MCP server.
Install the node
n8n Cloud: open a workflow, click the plus button and search for Adlane in the node panel. Select the verified Adlane node to add it.
Self-hosted: go to Settings → Community Nodes → Install, enter the package name below, accept the community node notice and install. Restart if your instance asks for it.
n8n-nodes-adlaneConnect your Adlane account
Add the Adlane node, choose Create new credential under Adlane OAuth2 API and click Connect my account. n8n discovers Adlane’s authorization server at
https://adlane.app/oauth/n8nfor the API resourcehttps://adlane.app/v1and registers its own callback. Sign in, review the two requested permissions on the consent screen (profile:readandads:read) and approve.No API key, client secret or access token goes into a workflow field. The credential uses PKCE and refresh tokens, and n8n stores and refreshes it for you.
Upgrading from 1.x or 2.x: create a new Adlane OAuth2 API credential and reconnect it before running workflows. Version 3 uses the REST resource at
adlane.app/v1with its own OAuth audience, so tokens issued to the earlier MCP resource cannot be reused. Operation names and input fields are unchanged.Make sure accounts are connected in Adlane
The node reads the accounts already connected to your Adlane account. In the Adlane workspace open Settings → Connections, connect Google Ads or Meta Ads and choose the ad accounts you want to report on. You can revoke n8n’s access at any time under Manage connected apps.
Run your first operation
Choose the Advertising account resource and List Ad Accounts to get account IDs, currency and timezone. Then add a second Adlane node with Get Campaign Performance, map the account ID and set an inclusive start and end date. Replace the manual trigger with a Schedule trigger when the output looks right.
Tip: each input item produces one output item with the response envelope. Use n8n’s Split Out node when you want one item per campaign.
OPERATIONS
Everything the node can do.
Five operations across three resources, each an ordinary HTTPS request to the Adlane REST API. All of them read data. The node cannot create campaigns, change budgets or bids, edit ads, publish creative or approve Adlane proposals. Any change to a live campaign still goes through the reviewed proposal flow in the Adlane workspace.
Account
The signed-in Adlane account. Useful for a first connection check.
get_profileGet profileRead the profile of the Adlane account that authorised n8n. It does not look up other people. GET /v1/account
Workspace
Businesses you set up in Adlane. Each one groups conversations, research and connected accounts.
list_workspacesList workspacesList the workspaces owned by the signed-in account, with website, goal and market. GET /v1/workspaces
Advertising account
Google Ads and Meta Ads accounts connected to your Adlane account, plus their campaigns and metrics.
list_ad_accountsList ad accountsRead connected advertising accounts with provider, currency and timezone. Use the returned account ID in the campaign operations. Return all or set a limit. GET /v1/ad-accountsget_campaign_detailsGet campaign detailsBrowse campaign status and configuration in a connected account. The node follows paging for you. GET /v1/ad-accounts/:accountId/campaignsget_campaign_performanceGet campaign performanceRead campaign metrics between an inclusive start and end date in the account timezone, optionally for one campaign ID. Google costs are returned in micros; Meta spend is in account currency. GET /v1/ad-accounts/:accountId/performance
The node has no trigger of its own. Use n8n’s Schedule, Webhook or Manual trigger to start a workflow, then add the Adlane node as an action. The node can also be used as a tool by n8n AI agents.
RECIPES
Six workflows to start from.
Illustrative examples. Adapt dates, thresholds and destinations to your own accounts.
Daily ads report to Slack
Schedule trigger every morning. Get campaign performance for yesterday on each connected account, format spend, clicks and conversions per campaign, and post one message to a Slack channel.
Schedule → Adlane → Code → SlackWeekly email digest
Every Monday, read the previous seven days for Google and Meta, build a short HTML table per provider, and send it with Gmail or SMTP. Keep Google and Meta conversions in separate columns.
Schedule → Adlane → HTML → GmailSpend and conversion anomaly alerts
Run hourly or daily. Compare yesterday with the trailing average you store in a Data Table or Sheet, and send an alert when spend jumps or conversions drop past your threshold.
Schedule → Adlane → IF → Slack or emailGoogle Sheets export
Append daily campaign rows to a Google Sheet for a long-running history you can chart. Convert Google cost micros to currency before writing, and keep the account timezone with each row.
Schedule → Adlane → Split Out → Google SheetsClient reports for agencies
Loop over ad accounts, read each client’s month to date, and send a report per client with your own template. One workflow, one credential, every account you can access.
Schedule → Adlane → Loop Over Items → EmailCampaign status audit
List campaign details for an account each week and record status changes in Notion, Airtable or a database, so you can see when campaigns were paused or enabled without logging into either ads platform.
Schedule → Adlane → Compare Datasets → NotionWHY N8N
Why pair Adlane with n8n?
Scheduled, not manual
n8n runs your reporting on a schedule. Adlane supplies the campaign evidence; n8n handles the timing, formatting and delivery.
One credential for both platforms
Google Ads and Meta Ads data come through one Adlane OAuth connection. No developer tokens or provider API keys inside n8n.
Read-only by design
Every operation reads data. The node cannot create campaigns, change budgets, edit ads or approve Adlane proposals.
Hundreds of destinations
Slack, Gmail, Google Sheets, Notion, Airtable, webhooks and any HTTP API. Build the report once and send it anywhere n8n can reach.
Reading the numbers correctly
Units and currency
Google costs are returned in micros: divide by 1,000,000 for the account currency. Meta spend is already in account currency. Keep each account’s currency and timezone with the row.
Attributed conversions
Conversions are attributed by each provider and can change after the report date. Do not add Google and Meta conversions together as unique sales.
Pagination and limits
List operations offer Return All or a Limit (default 50) and the node follows paging tokens for you. Your Adlane plan limits and account permissions still apply to every request.
Build your first ads report workflow.
Install n8n-nodes-adlane, connect your Adlane account and schedule the report your team keeps asking for. Prefer to ask questions instead of building workflows? Use the Adlane MCP server from your AI assistant.