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 manage records within tables in Pipefy. Specifically, for the Table Record - Delete operation, it deletes a record identified by its Record ID from a specified table.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or incorrect data entries in Pipefy tables.
- Integrating Pipefy with other systems to synchronize and maintain consistent data by removing records when they are deleted elsewhere.
- Managing workflows that require conditional deletion of records based on external triggers or business logic.
Practical example:
- A workflow that monitors a CRM system and deletes corresponding Pipefy table records when a customer is removed from the CRM.
Properties
| Name | Meaning |
|---|---|
| Record ID | The unique identifier of the table record to delete. This is required to specify which record should be removed. |
Output
The output JSON contains the result of the delete operation:
{
"success": true
}
success: A boolean indicating whether the deletion was successful (true) or not (false).
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Pipefy API via an API key credential configured in n8n.
- The node sends GraphQL mutation requests to the Pipefy API endpoint at
https://api.pipefy.com/graphql. - Proper permissions on the Pipefy account to delete table records are necessary.
Troubleshooting
Common issues:
- Invalid or missing Record ID: The operation will fail if the Record ID is not provided or incorrect.
- Insufficient permissions: The API key used must have rights to delete records; otherwise, the request will be denied.
- Network or API errors: Connectivity issues or Pipefy API downtime can cause failures.
Error messages:
- Errors returned from the API typically include messages about invalid IDs or authorization failures.
- If the node throws an error related to the GraphQL mutation, verify the Record ID and API credentials.
Resolution tips:
- Double-check the Record ID input for correctness.
- Ensure the API key credential has appropriate permissions.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.