Actions32
- Card Actions
- Organization Actions
- Pipe Actions
- Phase Actions
- Table Actions
- Table Record Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy API to manage tables within an organization. Specifically, the "Delete" operation for the "Table" resource allows users to delete a table by its ID. This is useful in scenarios where you need to programmatically remove obsolete or unwanted tables from your Pipefy workspace as part of automation workflows.
Practical examples:
- Automatically clean up tables that are no longer needed after a project ends.
- Remove test or temporary tables created during workflow testing.
- Manage organizational data lifecycle by deleting tables based on certain triggers or conditions.
Properties
| Name | Meaning |
|---|---|
| Table ID | The unique identifier of the table to delete |
Output
The output JSON contains a single field indicating whether the deletion was successful:
{
"success": true
}
success: A boolean value indicating if the table was successfully deleted (true) or not (false).
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Pipefy API.
- The node makes GraphQL requests to the Pipefy API endpoint at
https://api.pipefy.com/graphql. - Proper permissions are required on the API key to delete tables within the target organization.
Troubleshooting
Common issues:
- Invalid or missing Table ID: Ensure the Table ID provided is correct and exists.
- Insufficient permissions: The API key must have rights to delete tables.
- Network or API errors: Check connectivity and Pipefy service status.
Error messages:
- Errors returned from the API will typically include messages about invalid IDs or permission denied.
- If the node throws an error, verify the Table ID parameter and API credentials.
- Use the "Continue On Fail" option in n8n to handle errors gracefully in workflows.