Actions15
- Table Actions
- Table Record Actions
Overview
The node interacts with Pipefy's database tables and records, enabling advanced data operations such as creating, updating, retrieving, and deleting tables and their records. Specifically, the "Table - Get Many" operation fetches multiple tables within a specified organization, allowing users to retrieve an overview of all tables they have access to in that organization.
This operation is beneficial when you want to list or manage multiple tables at once, for example:
- Displaying all project management boards (tables) within a company.
- Synchronizing table metadata with another system.
- Automating reporting or auditing processes across multiple tables.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The unique identifier of the organization from which to retrieve multiple tables. |
| Limit | Maximum number of tables to return (between 1 and 50). |
Output
The output is an array of JSON objects, each representing a table within the specified organization. Each table object contains detailed information such as its ID, name, description, color theme, authorization level, and other metadata related to the table.
Example structure of one table item (simplified):
{
"id": "string",
"name": "string",
"description": "string",
"color": "string",
"publicForm": true,
"authorization": "read" | "write" | "admin",
// ... other table properties
}
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Pipefy service.
- Requires an additional API authentication token credential specific to Pipefy integration.
- The node uses GraphQL queries/mutations internally to communicate with Pipefy's API.
- The user must provide a valid Organization ID to fetch tables.
Troubleshooting
- Missing or invalid Organization ID: The operation requires a valid Organization ID. If missing or incorrect, the node will throw an error indicating the required field is missing.
- API authentication errors: Ensure that the API credentials are correctly configured and have sufficient permissions to access the organization's tables.
- Limit value out of range: The limit must be between 1 and 50. Setting a value outside this range may cause errors or unexpected behavior.
- Network or API downtime: Temporary network issues or Pipefy API outages can cause request failures. Retrying after some time or checking API status is recommended.