Editor super slow with Airtable nodes

Questions
1

Hi there. We’ve been experiencing issues with the editor for a while. We’ve rescaled our resources to 32GB and 16vCPUs, and still n8n is superslow. But We just realized something suprising:

When working with Airtable nodes, for single or multi-select data, n8n stores every possible option, even if you are not using it. If i’m updating a single-select column, selecting just one option, if I download the scenario’s JSON, I can see all the options.

In the sample scenario I show, the JSON weights 2.2MB, with just two nodes. These Airtable tables have several columns with thousands of options.

Is there a way to force n8n not to store these values? It’s good that, when you need to make a change, n8n retrieves them, but after that, It’s not necessary to store them.

image
image757×428 18.9 KB

(I cannot even upload this sample workflow here, it has 66k lines)

Information on your n8n setup

  • n8n version: Version 1.83.2
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): v1
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: We use n8n in all types of OS
2

It seems like this is the standard response format from Airtable. Also I don’t see any option on their API docs to change that behavior. You could use the “SET” node after the Airtable node to remove all unnecessary data from the JSON before processing it in further nodes.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.