Actions15
- Table Actions
- Table Record Actions
Overview
This node interacts with Pipefy database tables and their members, enabling advanced data operations such as creating, updating, retrieving, and deleting tables, as well as managing table members. Specifically, the "Get Members" operation for the "Table" resource retrieves the list of members associated with a specified table.
Common scenarios where this node is beneficial include:
- Managing team access by listing all members of a project or workflow table.
- Auditing user roles and permissions on specific tables.
- Integrating member data into workflows for notifications or reporting.
For example, you might use this node to fetch all users who have access to a particular table in Pipefy before sending them an update email or synchronizing their information with another system.
Properties
| Name | Meaning |
|---|---|
| Table ID | The unique identifier of the table whose members you want to retrieve. This is required. |
Output
The output JSON contains the detailed information about the members of the specified table. It typically includes member details such as user identifiers, roles, and related metadata as returned by the Pipefy API.
No binary data output is involved in this operation.
Example output structure (simplified):
{
"id": "table_id",
"members": [
{
"userId": "user_1",
"email": "user1@example.com",
"role": "admin"
},
{
"userId": "user_2",
"email": "user2@example.com",
"role": "member"
}
]
}
Dependencies
- Requires an API key credential for authenticating requests to the Pipefy API.
- Requires a Pipefy-specific API authentication token.
- The node uses internal utility functions to perform GraphQL queries/mutations against the Pipefy API.
Troubleshooting
- Missing or invalid Table ID: The operation requires a valid Table ID. If omitted or incorrect, the node will throw an error indicating that the Table ID is required.
- API authentication errors: Ensure that the API credentials are correctly configured and have sufficient permissions to access table member data.
- Network or API errors: Temporary network issues or Pipefy API downtime can cause failures. Retrying after some time or checking API status may help.
- Malformed response: If the Pipefy API changes its schema, the node might fail to parse the response correctly.