Overview
The ProAbono Trigger node listens for various events from the ProAbono subscription management platform via webhooks. It enables workflows to react automatically when specific customer, subscription, invoice, credit note, or payment method events occur in ProAbono.
Typical use cases include:
- Automating follow-up actions when a new customer is added.
- Triggering notifications or updates when subscriptions start, renew, or are suspended.
- Handling invoice lifecycle events such as payments, refunds, or overdue notices.
- Responding to changes in payment methods or credit notes issuance.
For example, you could use this node to send a welcome email whenever a new customer is added or to alert your finance team if an invoice payment fails.
Properties
| Name | Meaning |
|---|---|
| Customer Events | Select one or more customer-related events to listen for, such as: - Customer Added - Billing Address Updated - Payment Method Updated - Billing Succeeded/Failed - Charging Succeeded/Pending/Failed - Customer Suspended/Enabled/Grey Listed |
| Subscription Events | Select one or more subscription-related events to listen for, including: - Subscription Started/Renewed/Restarted - Suspended by Agent or due to Payment Issues - Terminated or Deleted - Features Updated or Upgraded - Term Date Updated |
| Invoice Events | Select one or more invoice-related events, such as: - Invoice Issued (automatic or offline payment) - Paid, Refunded, Cancelled - Auto Payment Failed or Authentication Requested - Overdue, Disputed, Uncollectible |
| Credit Notes Events | Listen for credit note issuance events, which occur when invoices are cancelled or refunded. |
| Payment Method Events | Listen for payment method status events, including: - Payment Information Expiring Soon or Expired - Defective Payment Methods - Insufficient Funds or Multiple Payment Issues |
Output
The node outputs JSON data representing the event payload received from ProAbono's webhook. This payload contains detailed information about the triggered event, such as customer details, subscription status, invoice data, or payment method information depending on the event type.
The output structure varies based on the event but generally includes all relevant fields sent by ProAbono for that event.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the ProAbono API.
- The node registers and manages a webhook URL with ProAbono to receive event notifications.
- The webhook security key and verification process ensure secure communication between ProAbono and n8n.
- No additional external dependencies beyond the ProAbono API and webhook infrastructure.
Troubleshooting
- Webhook Verification Failure: If the webhook signature or key does not match, events will be rejected. Ensure the webhook security key is correctly configured and that ProAbono sends valid signatures.
- Missing or Incorrect API Credentials: The node requires valid API credentials to register the webhook and fetch sample events. Verify that the API key is correct and has necessary permissions.
- Event Not Triggering: Confirm that the selected events in the node properties match those configured in ProAbono and that the webhook is active.
- 404 Errors on Webhook Check: Indicates the webhook may have been deleted or is invalid. Recreate the webhook by re-saving the node or workflow.
- Delayed Event Reception: Network issues or ProAbono service delays can cause late event delivery. Check ProAbono status and webhook logs.
Links and References
- ProAbono Official Website
- ProAbono API Documentation (generic link, replace with actual if available)
- n8n Webhook Node Documentation
- Webhook Security Best Practices
This summary is based solely on static analysis of the provided source code and property definitions.