Actions32
- Card Actions
- Organization Actions
- Pipe Actions
- Phase Actions
- Table Actions
- Table Record Actions
- User Actions
- Webhook Actions
Overview
This node interacts with the Pipefy API to manage records within tables in Pipefy. Specifically, the Update Table Record operation allows users to update an existing record in a specified table by providing the record ID, a new title, and updated field values.
Common scenarios where this node is beneficial include:
- Automating updates to project or process data stored in Pipefy tables.
- Synchronizing external data sources with Pipefy records.
- Modifying record details programmatically based on workflow conditions.
For example, you might use this node to update the status or priority fields of a task record in a Pipefy table when certain conditions are met in your workflow.
Properties
| Name | Meaning |
|---|---|
| Record ID | The unique identifier of the table record to update. |
| Title | The new title for the record. |
| Fields | The fields to update on the record. Each field requires: |
| - Field ID: The unique identifier of the field to update. | |
| - Value: The new value for the field (string). | |
| - Array Values: Comma-separated string values for fields that accept arrays (e.g., tags). |
Output
The output JSON contains the updated table record information with the following structure:
id: The unique identifier of the updated record.title: The updated title of the record.fields: An array of fields with their updated values, each containing:name: The name of the field.value: The updated value of the field (if applicable).array_value: The updated array values for fields that support multiple entries.
updated_at: Timestamp indicating when the record was last updated.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Pipefy API via an API key credential configured in n8n.
- The node sends GraphQL requests to the Pipefy API endpoint (
https://api.pipefy.com/graphql).
Troubleshooting
- Invalid Record ID: If the provided Record ID does not exist or is incorrect, the API will return an error. Verify the Record ID before running the node.
- Field ID Mismatch: Ensure that the Field IDs used in the "Fields" property correspond exactly to the fields defined in the target table.
- Incorrect Field Values: For array-type fields, provide comma-separated values correctly; otherwise, the update may fail or produce unexpected results.
- API Authentication Errors: Make sure the API key credential is valid and has sufficient permissions to update table records.
- GraphQL Syntax Issues: The node constructs GraphQL mutations dynamically; malformed inputs could cause errors. Validate input formats carefully.
If the node throws errors, enabling "Continue On Fail" can help isolate problematic items without stopping the entire workflow.