It would help if there was a node for:
Adding comments to Airtable records using the existing Airtable node.
The Airtable API provides an official endpoint for creating comments on records:
POST /v0/{baseId}/{tableIdOrName}/{recordId}/comments
My suggestion would be to add this as a new operation to the existing Airtable v2 node:
Resource: Record
Operation: Create Comment
The operation would require:
-
Base
-
Table
-
Record ID
-
Comment text
My use case:
I use Airtable as part of automated operational workflows where records are updated by n8n.
In some workflows, it would be useful to add a comment to a record instead of only changing field values. For example, an automation could add a comment when:
-
a workflow has processed a record
-
an external event or status change occurred
-
additional context should be attached to a record without modifying its fields
-
an automated process should leave a visible activity note for users working in Airtable
Currently this requires using the HTTP Request node even though Airtable supports the functionality through its official API.
Having this available directly in the Airtable node would make these workflows easier to configure and maintain.
Any resources to support this?
Airtable Web API documentation for record comments:
POST /v0/{baseId}/{tableIdOrName}/{recordId}/comments
Creating comments requires the Airtable scope:
data.recordComments:write
The existing Airtable v2 implementation is located here:
packages/nodes-base/nodes/Airtable/v2/actions/record
I would initially keep the scope small and only add Create Comment, rather than implementing the complete comments API at once.
One implementation question would be whether this should live under the existing Record resource or whether comments should eventually become their own Comment resource.
Are you willing to work on this?
Yes.
I’m happy to implement the operation and the corresponding tests.
Since the operation requires the additional data.recordComments:write scope, I would also appreciate guidance on how you would prefer the Airtable OAuth credential scope change to be handled.