$400 Bounty: Add Field IDs to n8n Airtable Node

[anglilian]

I’d like to request an enhancement for the Airtable node in n8n. Currently, the node requires field names when creating or updating records, but Airtable’s API uses field IDs. This can cause issues, especially when field names change or contain special characters, breaking workflows.

A similar functionality for targeting tables by ID instead of table name has been discussed and implemented (see this thread), and having a similar feature for fields would be extremely useful. There was a similar feature request here 1, but it hasn’t received much traction.

Proposed Solution:

• Add an option for the Airtable node to accept field IDs instead of field names for creating and updating records.
• In the n8n UI, the fields should still display the field names for easy configuration, but the underlying logic should use the field IDs, making workflows more resilient to Airtable schema changes.

Functional Requirements

• The Airtable node should allow field IDs for both the “Create” and “Update” operations.
• The UI should display field names during configuration but use field IDs in API calls.

Compatibility & Documentation

• Ensure the feature supports all Airtable data types and includes proper error handling.
• Update documentation to explain how to use the feature and any toggle options for field name vs. field ID.

Testing

• Provide test cases showing the feature works with field name changes and special characters.
• Include a basic workflow test that demonstrates functionality for both single and batch records.

Review

• The feature is merged into the main branch and works

Bounty: I am offering $400 for this, but I am open to negotiation based on complexity and feedback. If you are interested or would like clarification, please reach out [email protected]

[pnogemane]

close #19

[pnogemane]

/boss $400 verify

[domdomegg]

Hi @pnogemane Yep happy for you to attempt this. We'll pay the bounty once this is merged into the n8n main branch and works :)

[pnogemane]

Noted I have reopened the pull request. I am waiting for the reviews to be completed and I will advise as soon as the branch is tested and merged

[pnogemane]

Hi @pnogemane Yep happy for you to attempt this. We'll pay the bounty once this is merged into the n8n main branch and works :)

The branch has been scheduled for review. I will keep you updated on the progress

[pnogemane]

Hi @anglilian anglilian I have implemented the required changes as per pull request and a review has been conducted. The branch is now able merge.

[domdomegg]

Great thanks for the update that it is ready to merge! We'll pay the bounty once it is actually merged, as it will require approval by the n8n team etc. :)

[pnogemane]

Great thanks for the update that it is ready to merge! We'll pay the bounty once it is actually merged, as it will require approval by the n8n team etc. :)

Hello @domdomegg the branch has been merged successfully -

[pnogemane]

/boss $400

[pnogemane]

Merged

See pull Request : pnogemane/n8n-Add-option-to-use-field-IDs-in-Airtable-node#2

[domdomegg]

Hi @pnogemane, we'll pay the bounty once this is merged into the n8n main branch and works :)

I believe you've merged it into your own copy of the repo, not the n8n branch. Merging it into n8n will likely require the approval of the n8n maintainers.

[pnogemane]

Hello @domdomegg

I hope you are well. This is the final stage of the work. I sent through a code review and it was reviewed and approved by the maintainers.

The changes had to then wait in line before being merged to the n8n branch. But finally they where. At this point I think its fair to pay. Thank you and much appriciated.

[domdomegg]

Hi @pnogemane, as far as I can see you appear to have merged a branch into your own repo, but the one into the n8n branch has not been merged. I might have misunderstood what has happened - could you clarify where the code has been merged into the n8n branch itself?