Facebook Lead Ads Trigger throws "Unsupported get request" error when receiving a lead

Questions
1

Describe the problem/error/question

I finally managed to connect the Facebook Lead Ads Trigger to the Meta app (both the app and the workflow are live).

When using the Lead Ads test tool to send a test lead, an execution pops up in n8n but runs into the error below.

Does anyone have an idea what might still be missing? Another permission?

The app has advanced permissions for public_profile and standard permissions for the rest; the Lead Ads Test tool shows everything “green” for the app.

Thanks a lot.

What is the error message (if any)?

Problem in node ‘Facebook Lead Ads Trigger‘

Unsupported get request. Object with ID ‘1455016069442115’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api

Please share your workflow

Share the output returned by the last node

Screenshots

image
image998×973 66.1 KB

image
image2207×1268 143 KB

Error details

From Facebook Lead Ads Trigger
Error code

400

Full message

{ “error”: { “message”: “Unsupported get request. Object with ID ‘1455016069442115’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api”, “type”: “GraphMethodException”, “code”: 100, “error_subcode”: 33, “fbtrace_id”: “AZbM_h8EA4BPpob6sz3iOIN” } }
Other info
Node type

n8n-nodes-base.facebookLeadAdsTrigger

Node version

1 (Latest)

n8n version

2.14.2 (Self Hosted)

Time

1.4.2026, 14:07:22

Stack trace

NodeApiError: Unsupported get request. Object with ID ‘1455016069442115’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api at WebhookContext.facebookApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/FacebookLeadAds/GenericFunctions.ts:44:9) at processTicksAndRejections (node:internal/process/task_queues:103:5) at WebhookContext.facebookEntityDetail (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/FacebookLeadAds/GenericFunctions.ts:163:9) at async Promise.all (index 0) at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/FacebookLeadAds/FacebookLeadAdsTrigger.node.ts:258:27 at async Promise.all (index 0) at WebhookContext.webhook (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/FacebookLeadAds/FacebookLeadAdsTrigger.node.ts:244:18) at WebhookService.runWebhook (/usr/local/lib/node_modules/n8n/src/webhooks/webhook.service.ts:464:8) at Object.executeWebhook (/usr/local/lib/node_modules/n8n/src/webhooks/webhook-helpers.ts:526:24)

Instance info
instance information

Debug info

core

  • n8nVersion: 2.14.2
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: postgres
  • executionMode: scaling (single-main)
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: b14dff60-0166-47d7-95ff-2e9187c3efcb

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: database

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-01T12:13:23.785Z

3

That object ID is the lead itself, so n8n gets the webhook notification fine but then fails when it tries to fetch the actual lead data. Make sure your app has the leads_retrieval permission approved in the Meta app dashboard, not just pages_manage_ads

4

Hi @achamm. Thanks for the hint.

The app has the leads_retrieval permission with a standard access level saying “ready”. The same is true for all other permissions, except for public_profile, which has extended access already. Do I need to apply for extended access for this to work?

image
image1272×187 22 KB

Thanks, @Benjamin_Behrens. It looks like all of your questions can be answered with “yes” :grin:

  • I did recently create the app.
  • I did recently change some permissions (e.g., public_profile).
  • The webhook seems to be registered fine, I assume, as otherwise there wouldn’t be an execution registered in n8n, I guess.
5

I would just to ensure that your request has the least chance of not working, since you changed permissions, it might’ve thrown it off too.

6

Hi @Cooky101 :waving_hand:

I wouldn’t focus on adding more permissions first.
Since n8n is already receiving the webhook, the issue seems to happen in the second step, when it tries to fetch the actual lead data from Meta. Because you recently created the app and changed permissions, I’d reconnect the Facebook Lead Ads credentials in n8n, make sure the app is in Live mode, then republish the workflow and test again.
I’d also double-check that the Page, the form, and the account used to authorize the credential all belong to the same business setup. That kind of mismatch can still let the webhook arrive, but fail when n8n tries to read the lead details.

7

Yeah i get the same error, even the graph api doesnt find me the leads. It’s weird. Maybe u find any solution ?

8

welcome to the n8n community @lucimuaythai
Could you please post your question under Find Open Questions and select New? That way, we can review your case properly.

10

Before, like months ago, u didn t need leads_retrieval to be extended access. Am i correct?

În mie., 13 mai 2026 la 16:57, Jay Nguyen (Nguyễn Thiệu Toàn) <notifications@n8n.discoursemail.com> a scris:

11

You’re correct - before mid-2024, leads_retrieval only needed Standard Access (or worked in Development mode for test apps). Meta changed this: as of their 2024 enforcement wave, leads_retrieval now requires Extended Access for production use. In Development mode you can still test with app admins/testers, but any real lead from a live ad will hit the permission wall. To get Extended Access, go to App Review > Permissions and Features, find leads_retrieval, and submit a review request with a screencast showing your use case. Meta usually approves it within a few days for legitimate lead gen workflows.

12

Hi @Cooky101, thanks for opening this thread. I’ve the same problem and I’m interested in your solution. Could you fix it?

Best, Sebastian

13

Hi @Sebastian_Strauss. I have in fact resolved it using a workaround. Thus I was not actively following up on the solution proposals here and can’t say if they work or not.

What I did: I set the ads manager to write all leads into a google sheet (which it can do natively) and then used a google sheets trigger to transfer these leads into my crm.

This works pretty well. At least as long as you don’t have many lead forms in parallel. There will be a separate sheet per form and the trigger can only handle a single sheet. Thus, you’d need multiple triggers, and then the sheets api will run into rate limits.

Best regards