Actions55
- Webhooks Actions
- Payments Actions
- Products Actions
- Plans Actions
- Partner Referrals Actions
- Reporting Actions
- Orders Actions
- Subscriptions Actions
- Invoicing Actions
- Disputes Actions
Webhooks → Delete Webhook
AI-generatedOverview
The node provides enhanced integration with PayPal, supporting a wide range of operations across multiple PayPal resources. Specifically for the Webhooks - Delete Webhook operation, it allows users to delete an existing webhook by its ID. This is useful for managing webhook notifications and cleaning up unused or obsolete webhooks in your PayPal account.
Common scenarios include:
- Removing webhooks that are no longer needed to prevent unnecessary event notifications.
- Managing webhook lifecycle programmatically as part of automation workflows.
- Ensuring security by deleting webhooks that may have been compromised or misconfigured.
Example: Automatically delete a webhook after a certain event or condition is met in your workflow to maintain a clean webhook setup.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the webhook to delete. |
| Additional Options | Collection of optional parameters: - Environment: Choose between "Sandbox" or "Live". - Page Size: Number of items per page (used in list operations). - Start Time: Filter start date/time (ISO 8601 format). - End Time: Filter end date/time (ISO 8601 format). |
Note: For the Delete Webhook operation, only the ID and optionally Environment from Additional Options are relevant.
Output
The node outputs a JSON object containing:
resource: The resource name, here"webhooks".operation: The operation performed, here"deleteWebhook".success: Boolean indicating if the deletion was successful (true).- Other fields returned by the PayPal API response related to the deletion.
creditsUsed: Number of API credits consumed by this operation.creditsRemaining: Remaining API credits after the operation.timestamp: ISO string timestamp when the operation was executed.
No binary data output is produced by this operation.
Dependencies
- Requires valid credentials for:
- An API key credential for the external "N8N Tools" API used for validation.
- A PayPal OAuth2 API credential providing an access token and environment info.
- The node makes HTTP requests to both the N8N Tools API and the PayPal REST API endpoints.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Invalid JSON in request body: If a request body is provided but contains invalid JSON, the node will throw an error. Ensure JSON syntax correctness.
- Validation failure: If the N8N Tools API validation fails, the node will stop with an error message indicating validation failure.
- Unknown operation or resource: Using an unsupported operation or resource will cause an error. Verify the operation and resource names.
- API authentication errors: If PayPal OAuth2 credentials are missing or expired, the node will fail. Refresh tokens or reauthenticate as needed.
- HTTP request failures: Network issues or incorrect API URLs can cause failures. Check connectivity and credential configurations.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.