Actions10
- Order Actions
- Payment Link Actions
- Payment Actions
- Refund Actions
- Settlement Actions
- Invoice Actions
- Dispute Actions
Overview
This node interacts with Razorpay's API to manage disputes related to payments. Specifically, the "Fetch All" operation under the "Dispute" resource retrieves a list of all disputes associated with your Razorpay account. This is useful for financial reconciliation, monitoring chargebacks, or automating dispute management workflows.
Practical examples include:
- Automatically fetching all current disputes to analyze their status.
- Integrating dispute data into accounting or CRM systems.
- Expanding dispute details to get more context on each case for better decision-making.
Properties
| Name | Meaning |
|---|---|
| Additional Options | Optional settings to customize the fetch operation. |
| Expand Details | Choose specific additional information to include in the response: - Payment Details: Expand payment details for each dispute. - Transaction Settlement Details: Expand transaction settlement details for each dispute. |
Output
The node outputs an array of JSON objects representing disputes retrieved from Razorpay. Each object contains details about a single dispute, such as its ID, status, amount, and other relevant metadata.
If the "Expand Details" option is used, the output will include nested objects with expanded payment information or transaction settlement details, providing deeper insight into each dispute.
No binary data is output by this node.
Dependencies
- Requires a valid Razorpay API key credential configured in n8n to authenticate requests.
- The node depends on Razorpay's REST API endpoints for disputes.
- No additional external services are required beyond Razorpay.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
- Requesting expansions that are not supported or malformed parameters may result in API errors.
Error Messages:
"Unknown operation: ...": Indicates an unsupported operation was selected; ensure "Fetch All" is chosen for disputes.- Authentication errors typically mention invalid credentials or unauthorized access; verify API keys.
- Rate limiting or quota exceeded errors from Razorpay require waiting or adjusting usage.
Resolutions:
- Double-check API credentials and permissions.
- Confirm network access to Razorpay endpoints.
- Use the "Additional Options" carefully and according to Razorpay API documentation.