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 create a new record in a specified table within Pipefy. It is useful for automating data entry into Pipefy tables, enabling workflows that require adding structured records programmatically.
Typical use cases include:
- Automatically logging form submissions or external data into Pipefy tables.
- Creating records as part of a larger automation process involving Pipefy.
- Integrating other systems with Pipefy by pushing data into tables.
For example, you could use this node to create a new customer record in a Pipefy table whenever a new lead is captured on your website.
Properties
| Name | Meaning |
|---|---|
| Table ID | The ID of the Pipefy table where the record will be created. |
| Title | The title of the new record. |
| Fields | The fields to set on the record. This is a collection where each item includes: |
| - Field ID: The ID of the field to set. | |
| - Value: The value to assign to the field (string). | |
| - Array Values: Comma-separated values for array-type fields (e.g., multi-select fields). |
Output
The node outputs JSON data representing the newly created table record. The structure includes:
id: The unique identifier of the created record.title: The title of the record.fields: An array of fields with their details:name: The name of the field.value: The value assigned to the field.array_value: If applicable, an array of values for fields that accept multiple entries.
created_at: Timestamp when the record was created.
No binary data output is produced by 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
https://api.pipefy.com/graphql. - Proper permissions are needed on the Pipefy account to create records in the specified table.
Troubleshooting
- Invalid Table ID: If the provided Table ID does not exist or is incorrect, the API will return an error. Verify the Table ID is correct and accessible.
- Missing Required Fields: The API may reject the request if required fields are missing or invalid. Ensure all mandatory fields are included and properly formatted.
- Authentication Errors: If the API key credential is missing or invalid, authentication errors will occur. Confirm the API key is correctly set up in n8n credentials.
- Field Value Format: For array fields, ensure comma-separated values are correctly formatted without extra spaces unless intended.
- API Rate Limits: Excessive requests may trigger rate limiting. Implement retries or delays if necessary.