Actions15
- Table Actions
- Table Record Actions
Overview
This node operation updates an existing record in a Pipefy database table. It allows users to modify the title and field values of a specific table record identified by its unique ID. This is useful for workflows that need to keep Pipefy data synchronized with other systems or update records based on external triggers or inputs.
Practical examples:
- Automatically updating a customer status or details in Pipefy when a CRM record changes.
- Modifying task details in a Pipefy table as part of an automated approval process.
- Syncing form submission data into an existing Pipefy record with updated information.
Properties
| Name | Meaning |
|---|---|
| Table Record ID | The unique identifier of the table record to update. This is required to specify which record to modify. |
| Record Title | The new title for the table record. Optional; if provided, it will update the record's title. |
| Record Fields | A collection of fields to update on the record. Each entry requires: - Field ID: Identifier of the table field to update. - Value: New value to set for that field. Multiple fields can be updated at once. |
Output
The output JSON contains the updated table record object reflecting the changes made. This includes the record's ID, updated title (if changed), and updated field values. The structure matches the Pipefy table record format.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Pipefy API.
- Requires a Pipefy-specific API authentication token configured in n8n credentials.
- The node uses internal utility functions to perform GraphQL requests to Pipefy's API endpoints.
Troubleshooting
- Missing Required Fields: If "Table Record ID" is not provided, the node will throw an error indicating the missing required field. Ensure this ID is correctly set.
- Invalid Field IDs or Values: Providing incorrect field IDs or incompatible values may cause the update to fail silently or return errors from the API. Verify field IDs exist in the target table.
- JSON Parsing Errors: Although not applicable directly here (since record fields are structured inputs), ensure any JSON inputs used elsewhere are valid.
- API Authentication Errors: If credentials are invalid or expired, the node will fail to connect. Recheck API keys and tokens.
- Permission Issues: The authenticated user must have write permissions on the target table and record.