Overview
This node acts as a trigger for workflows based on events from the Polar platform. It listens for specific Polar webhook events and starts the workflow when one of those events occurs. This is useful for automating processes that depend on real-time updates from Polar, such as customer lifecycle changes, order processing, subscription management, or product updates.
Practical examples include:
- Automatically updating a CRM system when a new customer is created in Polar.
- Triggering an email notification when an order is paid.
- Syncing subscription status changes to another service.
- Logging refund events for accounting purposes.
Properties
| Name | Meaning |
|---|---|
| Events | Polar events that will trigger the workflow. Multiple options can be selected, including: Benefit Created, Benefit Grant Created, Benefit Grant Cycled, Benefit Grant Revoked, Benefit Grant Updated, Benefit Updated, Checkout Created, Checkout Updated, Customer Created, Customer Deleted, Customer State Changed, Customer Updated, Order Created, Order Paid, Order Refunded, Order Updated, Organization Updated, Product Created, Product Updated, Refund Created, Refund Updated, Subscription Activated, Subscription Canceled, Subscription Created, Subscription Revoked, Subscription Uncanceled, Subscription Updated. |
| Secret | A secret string used to validate that incoming webhook requests genuinely come from Polar. This ensures security by verifying the authenticity of the webhook payloads. |
Output
The node outputs JSON data representing the verified webhook event received from Polar. The output contains the full event payload after successful verification of the webhook signature using the provided secret.
If the webhook request is valid, the output JSON array includes the event data exactly as sent by Polar, allowing subsequent nodes in the workflow to process this information.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Polar API.
- Needs configuration of the Polar environment (sandbox or production) via credentials.
- Uses a secret string configured in the node properties to verify webhook signatures.
- Relies on Polar's webhook endpoints to send event notifications.
Troubleshooting
- Webhook Verification Failure: If the secret does not match or the signature verification fails, the node will not trigger the workflow. Ensure the secret configured in the node matches exactly the secret set in the Polar webhook settings.
- Webhook Not Triggering: Confirm that the selected events in the "Events" property correspond to the actual events being sent by Polar. Also, verify that the webhook URL registered with Polar is correct and accessible.
- API Authentication Errors: If the node cannot create or check the webhook endpoint, verify that the API key credential is valid and has sufficient permissions.
- Webhook Endpoint Deletion Issues: Sometimes deleting the webhook endpoint may fail if it was already removed externally; this usually does not affect functionality but should be noted.
Links and References
- Polar API Documentation (for detailed info on events and webhook setup)
- n8n Webhook Node Documentation (general webhook usage in n8n)