Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node interacts with the Pipefy GraphQL API to manage webhooks. Specifically, the "Delete Webhook" operation allows users to remove an existing webhook from their Pipefy account. This is useful for cleaning up unused or obsolete webhooks to maintain an organized integration environment and prevent unnecessary event triggers.
Common scenarios include:
- Removing a webhook that is no longer needed after a workflow change.
- Deleting test webhooks created during development.
- Managing webhook lifecycle programmatically within automation workflows.
Example: A user wants to delete a webhook associated with a specific Pipe or Organization by providing its ID and type, ensuring that events from that webhook no longer trigger downstream processes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Pipefy API. Options: "Service Account" or "Personal Access Token". |
| Webhook ID | The unique identifier of the webhook to be deleted. This is required. |
| Type | The category of the webhook target. Options: "Org" (Organization) or "Pipe". |
Output
The node outputs a JSON array containing the result of the deletion operation for each input item. The exact structure depends on the API response but typically includes confirmation of successful deletion or error details if the operation failed.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Requires either a Service Account credential or a Personal Access Token credential configured in n8n for authentication.
- No additional external dependencies are indicated.
Troubleshooting
- Invalid Webhook ID: If the provided webhook ID does not exist or is malformed, the API will return an error. Verify the webhook ID before attempting deletion.
- Authentication Errors: Using incorrect or expired credentials will cause authentication failures. Ensure the API key or token is valid and has sufficient permissions.
- Permission Issues: The authenticated user must have rights to delete webhooks in the specified organization or pipe.
- Type Mismatch: Providing an incorrect type ("org" vs "pipe") may lead to failure in locating the webhook. Confirm the correct type matches the webhook's scope.