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 avoid 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 that was set up to listen to changes in a specific pipe or organization once the integration is no longer required.
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 a required string input. |
| Type | Specifies the scope of the webhook. Options: "Org" (organization-level webhook) or "Pipe" (pipe-level webhook). |
Output
The node outputs a JSON array containing the result of the deletion operation for each input item processed. Typically, this will include confirmation data or status indicating whether the webhook was successfully deleted.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Requires authentication via either a service account credential or a personal access token credential configured in n8n.
- No additional external dependencies are indicated.
Troubleshooting
- Invalid Webhook ID: If the provided webhook ID does not exist or is incorrect, the API will likely return an error. Verify the webhook ID before attempting deletion.
- Authentication Errors: Using invalid 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 the specified webhook. Lack of permissions will result in authorization errors.
- Type Mismatch: Specifying the wrong type ("org" vs "pipe") may cause the deletion to fail if the webhook does not belong to that category.
To resolve these issues:
- Double-check the webhook ID and type.
- Confirm that the credentials used are correct and active.
- Ensure the user associated with the credentials has appropriate permissions in Pipefy.
Links and References
- Pipefy API Documentation
- Pipefy Webhooks Guide (example link, replace with actual)