Actions37
- Offer Item Actions
- Customer Actions
- Dispute Actions
- Installment Actions
- Line Item Actions
- Offer Actions
- Payment Actions
- Payment Method Actions
- Payment Plan Actions
- Payment Schedule Actions
- Refund Actions
Overview
This node integrates with the Partially Payment Plans API to manage disputes related to payments. Specifically, the Dispute - List operation retrieves a list of disputes filtered by various criteria such as customer ID, date ranges, reason for dispute, and status.
Common scenarios where this node is beneficial include:
- Fetching all disputes for a specific customer to review their payment issues.
- Filtering disputes by status (e.g., "needs response" or "won") to prioritize handling.
- Retrieving disputes within a certain date range for reporting or auditing purposes.
Practical example:
- A merchant wants to automatically pull all disputes marked as "needs response" from the last month to trigger follow-up actions in their CRM system.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer whose disputes you want to list. |
| Additional Filters | A collection of optional filters to narrow down the disputes list: |
| - Date | Filter disputes by a specific date. |
| - Date Range Maximum | The maximum date for filtering disputes within a date range. |
| - Date Range Minimum | The minimum date for filtering disputes within a date range. |
| - Reason | The reason for the dispute. Possible values: customer_initiated, debit_not_authorized, duplicate, fraudulent, general, incorrect_account_details, insufficient_funds, other, product_not_received, product_unacceptable, subscription_canceled, subscription_not_received, unrecognized. |
| - Status | The current status of the dispute. Possible values: charge_refunded, charge_reversed, lost, needs_response, under_review, warning_closed, warning_needs_response, warning_under_review, won. |
Output
The node outputs an array of JSON objects representing disputes matching the specified filters. Each object contains detailed information about a dispute as returned by the Partially API, including fields such as dispute ID, customer ID, reason, status, dates, and other relevant metadata.
No binary data output is produced by this operation.
Dependencies
- Requires connection to the Partially Payment Plans API.
- Requires an API key credential configured in n8n for authenticating requests to the Partially API.
- No additional external dependencies are needed.
Troubleshooting
- Empty results: If no disputes are returned, verify that the filters (customer ID, date range, reason, status) are correctly set and that disputes exist matching those criteria.
- Invalid date format errors: Ensure date inputs are valid ISO 8601 date strings or compatible formats as expected by the node.
- Authentication errors: Confirm that the API key credential is correctly configured and has sufficient permissions.
- API rate limits or connectivity issues: Check network connectivity and API usage limits; retry after some time if rate limited.
Links and References
- Partially Payment Plans API Documentation (generic link, replace with actual if available)
- n8n documentation on Creating Custom Nodes