Open anglilian opened 1 month ago
close #19
/boss $400 verify
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 :)
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
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
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.
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. :)
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 -
/boss $400
Merged
See pull Request : https://github.com/pnogemane/n8n-Add-option-to-use-field-IDs-in-Airtable-node/pull/2
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:
Functional Requirements
Compatibility & Documentation
Testing
Review
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 anglilian@bluedot.org