Actions115
- Course Actions
- Bundle Actions
- Course Grade Actions
- Course Grade Detail Actions
- Course Teacher Actions
- Email Actions
- Email Campaign Actions
- Email Campaign Course Actions
- Email Campaign Excluded Course Actions
- Email Campaign Excluded List Actions
- Enroll Actions
- Email Campaign Excluded Plan Actions
- Email Campaign List Actions
- Email Campaign Plan Actions
- Email List Actions
- MindzPay Account Actions
- MindzPay Invoice Actions
- MindzPay Payment Actions
- MindzPay Subscription Actions
- Subscription Actions
- Team Actions
- User Actions
Overview
The MindzPay Invoice node's Reissue operation allows users to reissue an existing invoice within the MindzPay system. This is useful in scenarios where an invoice needs to be regenerated or resent, for example, if the original invoice was lost, expired, or requires updates without creating a new invoice from scratch.
Practical examples include:
- Reissuing an invoice after correcting billing details.
- Resending an invoice to a customer who did not receive the original.
- Regenerating an invoice for accounting or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Account Key | The key of the MindzPay account used to authenticate and identify the account context. |
| Invoice ID | The unique identifier of the invoice to be reissued. |
Output
The output of this node operation will be JSON data representing the reissued invoice details as returned by the MindzPay API. This typically includes updated invoice information such as invoice number, status, issue date, due date, amounts, and any other metadata related to the invoice.
If the node supports binary data output (not explicitly shown here), it would likely represent downloadable invoice files such as PDFs.
Dependencies
- Requires an active connection to the Mindz API authenticated via an OAuth2-based API key credential.
- The node depends on the MindzPay service being available and accessible.
- Proper configuration of the Mindz OAuth2 credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Account Key: Ensure the correct account key is provided.
- Incorrect Invoice ID: Verify that the invoice ID exists and belongs to the specified account.
- Authentication errors: Check that the OAuth2 credentials are valid and have not expired.
- Network or API downtime: Confirm MindzPay API availability.
Error messages:
- "Invoice not found": The provided Invoice ID does not exist or is inaccessible under the given account.
- "Unauthorized" or "Authentication failed": The API credentials are invalid or expired.
- "Invalid parameters": Required properties like Account Key or Invoice ID are missing or malformed.
Resolving these usually involves verifying input parameters, refreshing credentials, and ensuring network connectivity.
Links and References
- MindzPay API Documentation (replace with actual URL)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- General n8n Node Development: https://docs.n8n.io/integrations/creating-nodes/