I would also be interested in a similar feature and would be open to giving a bounty of $300 for it. 
Specifically, 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, 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 $300 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]