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

Sim, tenho o mesmo erro, até a API de gráficos não encontra os leads para mim. É estranho. Talvez você encontre alguma solução?

8

bem-vindo à comunidade n8n @lucimuaythai
Poderia postar sua pergunta em Find Open Questions e selecionar New? Dessa forma, podemos revisar seu caso adequadamente.

10

Antes, como meses atrás, você não precisava que leads_retrieval fosse acesso estendido. Estou correto?

Em qua., 13 de mai. de 2026 às 16:57, Jay Nguyen (Nguyễn Thiệu Toàn) <notifications@n8n.discoursemail.com> escreveu:

11

Você está certo - antes de meados de 2024, leads_retrieval precisava apenas de Acesso Padrão (ou funcionava em modo de Desenvolvimento para aplicativos de teste). Meta mudou isso: a partir de sua onda de aplicação em 2024, leads_retrieval agora requer Acesso Estendido para uso em produção. Em modo de Desenvolvimento você ainda pode testar com administradores de aplicativos/testadores, mas qualquer lead real de um anúncio ativo vai bater na parede de permissões. Para obter Acesso Estendido, vá para App Review > Permissions and Features, encontre leads_retrieval e envie uma solicitação de revisão com um screencast mostrando seu caso de uso. Meta geralmente aprova isso em alguns dias para fluxos de geração de leads legítimos.

12

Oi @Cooky101, obrigado por abrir este tópico. Tenho o mesmo problema e estou interessado na sua solução. Você conseguiu resolver?

Abraços, Sebastian

13

Oi @Sebastian_Strauss. Na verdade, resolvi usando um workaround. Por isso, não estava acompanhando ativamente as propostas de solução aqui e não consigo dizer se funcionam ou não.

O que fiz: configurei o gerenciador de anúncios para escrever todos os leads em uma planilha do Google (o que ele consegue fazer nativamente) e depois usei um gatilho do Google Sheets para transferir esses leads para meu CRM.

Isso funciona bem. Pelo menos enquanto você não tiver muitos formulários de lead em paralelo. Haverá uma planilha separada por formulário e o gatilho pode lidar com apenas uma planilha. Assim, você precisaria de múltiplos gatilhos e, então, a API do Sheets terá problemas com limites de taxa.

Atenciosamente