Facebook Lead node bug?

Questions
1

I think there are an issue/bag with Facebook Lead node.

If you select the Page or Form as a list it queries the Facebook API so bad that goes over the limit under 30 seconds.

If you use ID instead the API is happy.

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hi @kgurinov ,

Thanks for bringing this up! :muscle:
While I set up some credentials and try to replicate, could you share the error message that you get? Maybe the whole workflow if you’re comfortable with that.

Could you also fill in these details:

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
4

So it works fine as it is, you put credentials you go Select the Page from the list its automatically pulls the list for you but if you keep the list open you can see its constantly refreshing, it makes the API calls constantly to Facebook. It does the same if you put in in listen mode.
Facebook gives you 200 API calls per h and it uses all of them and then error out or timeout just to fetch the list.
When you switch to ID the API calls stops from going over the border and are in healthy state.
Hope it make sense.

5

Hi @kgurinov ,

Thanks for the details!

I was able to reproduce this and have passed it on internally so we can work on a fix. Meantime, like you said, using the ID search function doesn’t cause an overuse of lead limits and is currently the best workaround :slight_smile:

6

New version [email protected] got released which includes the GitHub PR 10956.