Actions15
- Table Actions
- Table Record Actions
Overview
This node enables managing records within Pipefy database tables, specifically focusing on creating new table records. It allows users to add a record with a title and multiple field values to a specified table in Pipefy. This is useful for automating data entry into Pipefy tables, integrating external data sources, or programmatically populating Pipefy databases as part of workflow automation.
Practical examples include:
- Automatically adding new customer information as records into a Pipefy table when a form is submitted.
- Creating task records in a project management Pipefy table based on triggers from other systems.
- Populating inventory or asset tracking tables with data imported from external databases or APIs.
Properties
| Name | Meaning |
|---|---|
| Table ID | The unique identifier of the Pipefy table where the new record will be created. |
| Record Title | (Optional) The title or name of the new table record. |
| Record Fields | A collection of field-value pairs representing the data to populate in the table record. Each item includes: - Field ID: Identifier of the specific field in the table. - Value: The value to assign to that field. |
Output
The node outputs JSON data representing the newly created table record. The output structure includes all details of the created record as returned by the Pipefy API, such as its ID, title, and field values.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Pipefy API.
- Requires a second API authentication token credential for accessing the n8n Tools API layer.
- The node uses GraphQL queries and mutations to interact with Pipefy's database tables and records.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing Required Fields: Errors occur if "Table ID" is not provided. Ensure this property is set correctly.
- Invalid Field IDs or Values: If field IDs do not exist in the target table or values are incompatible, the API may reject the request.
- API Authentication Failures: Verify that the API credentials are valid and have sufficient permissions.
- Malformed Record Fields: The "Record Fields" must be properly structured; otherwise, the request will fail.
- Network or API Errors: Temporary network issues or Pipefy API downtime can cause failures; retrying later may help.
Common error messages typically indicate missing required parameters or invalid input data. Reviewing the node's input properties and ensuring they match the Pipefy table schema usually resolves these errors.