Actions19
- Customer Actions
- Subscription Actions
- Invoice Actions
Overview
This node integrates with the ProAbono API to interact with various resources such as Customers, Subscriptions, and Invoices. Specifically, for the Invoice resource, it supports operations including retrieving a full credit note in PDF format. This is useful in scenarios where you need to programmatically access detailed credit note documents related to invoices, for example, to automate accounting workflows, generate reports, or archive financial documents.
A practical example would be an accounting automation workflow that fetches the full credit note PDF by its number to attach it to an email or store it in a document management system.
Properties
| Name | Meaning |
|---|---|
| Credit Note Full Number | The unique full number of the credit note to retrieve, formatted like "FA001-000000023". This is not an internal ID but the external reference number used to identify the credit note. |
Output
The node outputs JSON data representing the response from the ProAbono API. For the "Retrieve Full Credit Note (PDF)" operation, the output will include the binary content of the credit note PDF file. This binary data can be used downstream in the workflow to save the PDF, send it via email, or process it further.
Dependencies
- Requires an active ProAbono account.
- Needs API credentials: an agent key and an API key for authentication.
- The node uses the business ID from credentials to construct the base URL for API requests.
- Proper configuration of these credentials in n8n is necessary for successful API communication.
Troubleshooting
- Invalid Credit Note Number: If the provided credit note full number does not exist or is malformed, the API may return an error indicating the credit note was not found. Verify the number format and existence.
- Authentication Errors: Incorrect or missing API keys will cause authentication failures. Ensure the API credentials are correctly set up in n8n.
- Network Issues: Connectivity problems to the ProAbono API endpoint can cause request failures. Check network access and firewall settings.
- Permission Denied: Insufficient permissions associated with the API keys might prevent access to certain resources. Confirm that the API keys have the required scopes.
Links and References
- ProAbono API Documentation (for detailed API endpoints and usage)
- n8n Documentation (for general guidance on using credentials and handling binary data)