Actions15
- Table Actions
- Table Record Actions
Overview
This node enables interaction with Pipefy database tables, specifically allowing users to retrieve detailed information about a single table by its ID. It is useful in scenarios where you need to fetch the metadata and configuration of a specific Pipefy table within an automation workflow.
For example, you might use this node to:
- Retrieve a table's structure before processing or updating its records.
- Verify the existence and properties of a table before performing further operations.
- Integrate Pipefy table data into other systems by fetching table details dynamically.
Properties
| Name | Meaning |
|---|---|
| Table ID | The unique identifier of the Pipefy table to retrieve. This is required to specify which table's details should be fetched. |
Output
The output JSON contains the full details of the requested Pipefy table. This includes all metadata and configuration fields as returned by the Pipefy API for that table. The exact structure depends on the Pipefy API response but typically includes fields such as the table's name, description, color, authorization level, public form status, and other relevant attributes.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Pipefy service.
- Requires an additional API authentication token credential for the n8n Tools API.
- The node uses internal utility functions to perform GraphQL queries/mutations against the Pipefy API.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing or invalid Table ID: The node requires a valid Table ID. If omitted or incorrect, it will throw an error indicating the missing required field.
- Authentication errors: Ensure that the API credentials are correctly set up and have sufficient permissions to access the Pipefy tables.
- API request failures: Network issues or Pipefy API downtime can cause request failures. Check connectivity and Pipefy service status.
- Invalid response structure: If Pipefy changes their API schema, the node may fail to parse the response correctly. Updating the node or checking for updates from the developer may be necessary.