Actions10
- Order Actions
- Payment Link Actions
- Payment Actions
- Refund Actions
- Settlement Actions
- Invoice Actions
- Dispute Actions
Overview
This node integrates with a payment platform to fetch invoices related to a specific subscription. The "Fetch Invoices for Subscription" operation retrieves all invoices associated with a given subscription ID. This is useful for financial reconciliation, auditing, or displaying billing history for customers in subscription-based services.
Practical examples include:
- Automatically retrieving all invoices for a customer's subscription to display in a customer portal.
- Exporting invoice data for accounting or reporting purposes.
- Triggering follow-up actions based on invoice status or amounts.
Properties
| Name | Meaning |
|---|---|
| Subscription ID | Unique identifier of the subscription to fetch invoices for (e.g., sub_00000000000001). |
Output
The node outputs an array of JSON objects representing invoices linked to the specified subscription. Each object contains detailed invoice data as returned by the payment platform's API, such as invoice ID, amount, status, dates, and other relevant metadata.
If the node supports binary data output (not indicated here), it would typically represent downloadable invoice PDFs or attachments, but this operation focuses on JSON invoice data only.
Dependencies
- Requires an API key credential for authenticating with the payment platform.
- The node depends on the payment platform's API being accessible and the subscription ID being valid.
- No additional environment variables are explicitly required beyond standard API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing subscription ID will result in errors or empty results.
- Network or authentication failures can cause request errors.
- If the subscription has no invoices, the output may be an empty array.
Error messages:
"Unknown operation": Indicates the selected operation is not recognized; ensure "Fetch Invoices for Subscription" is chosen.- API errors related to invalid credentials or permissions should be resolved by verifying the API key and access rights.
- Timeout or connectivity errors require checking network access to the payment platform.
Links and References
- Refer to the payment platform’s official API documentation for invoices and subscriptions to understand the data structure and available fields.
- n8n documentation on creating and using API credentials for secure authentication.