Overview
This node acts as a webhook trigger for Pinch events, allowing workflows to respond automatically when specific events occur within the Pinch platform. It listens for various event types such as creation or updates of payers, subscriptions, payments, refunds, disputes, compliance changes, and more.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a new payer is created.
- Triggering notifications or data synchronization when subscriptions are updated or completed.
- Handling payment lifecycle events like payment creation or refund processing.
- Monitoring compliance status changes for merchants.
- Reacting to dispute creation or updates for fraud management.
For example, you could use this node to start a workflow that sends an email notification whenever a subscription is cancelled or to update your CRM system when a refund is created.
Properties
| Name | Meaning |
|---|---|
| Events | The event(s) to listen to. Multiple events can be selected. Options include: - All (any event triggered) - Payer Created - Payer Updated - Subscription Cancelled - Subscription Created - Subscription Complete - Bank Results - Scheduled Process - Transfer - Realtime Payment - Payment Created - Refund Created - Refund Updated - Compliance Updated - Dispute Created - Dispute Updated - Merchant Compliance Updated |
Output
The node outputs JSON data representing the webhook payload received from Pinch for the triggered event. The output structure corresponds directly to the event's data as sent by Pinch, typically including details relevant to the event type (e.g., payer info, subscription details, payment status).
If the event type does not match the selected events or is undefined, the node outputs no data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Pinch API.
- Needs proper webhook URL configuration in n8n to receive incoming HTTP POST requests from Pinch.
- Relies on the Pinch API to create, verify, and delete webhook registrations.
Troubleshooting
- Webhook Not Triggering: Ensure the webhook URL is correctly set up and publicly accessible. Verify that the Pinch platform has registered the webhook successfully.
- Event Filtering Issues: If no data is received, check that the selected events in the node properties include the event types being sent by Pinch. Selecting "All" will listen to every event.
- API Errors During Webhook Setup: Errors during webhook creation or deletion may indicate invalid credentials or network issues. Confirm the API key is valid and the Pinch API is reachable.
- Unexpected Empty Output: This can happen if the incoming webhook event type is not among the selected events or missing in the payload.