Overview
This node acts as a webhook trigger for events from the Partially service. It listens for specific Partially events such as payment status changes, disputes, refunds, and plan updates. When one of these events occurs, the node receives the event payload via a webhook call, verifies its authenticity using a signature, and then triggers the workflow with the event data.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a customer abandons checkout.
- Handling dispute lifecycle events to update internal records or notify teams.
- Reacting to payment success or failure to manage subscriptions or access.
- Tracking plan status changes for billing or user management purposes.
For example, you could use this node to automatically send an email notification when a payment fails or to update your CRM when a refund is created.
Properties
| Name | Meaning |
|---|---|
| Event | The specific Partially event to listen for. Options: Checkout Abandoned, Dispute Closed, Dispute Created, Payment Failed, Payment Succeeded, Plan Defaulted, Plan Opened, Plan Paid, Refund Created |
Output
The node outputs the JSON payload received from the Partially webhook in the json field of the output data. This payload contains detailed information about the event that triggered the webhook, such as payment details, dispute information, or plan data depending on the event type.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests with the Partially service.
- Needs to be configured with a publicly accessible webhook URL so Partially can send event notifications.
- Uses HMAC SHA256 signature verification to ensure webhook payload integrity and authenticity.
Troubleshooting
- Missing Partially-Signature header: The node expects a specific HTTP header containing the webhook signature. If this header is missing, the node will throw an error. Ensure that the Partially service is correctly sending the signature header.
- Invalid webhook signature: If the computed HMAC signature does not match the signature sent in the header, the node rejects the webhook. This usually indicates a mismatch in the API key used or tampering with the payload. Verify that the correct API key is configured and that the webhook payload is unaltered.
- Webhook not found or creation issues: The node manages webhook registration with Partially. If webhooks are not properly registered or deleted, check network connectivity and API key permissions.
Links and References
- Partially API Documentation (hypothetical link)
- n8n Webhook Trigger Nodes
- HMAC SHA256 Signature Verification