Easybill icon

Easybill

Interact with Easybill API

Actions13

Overview

This node integrates with the Easybill API to manage attachments related to customers and documents. Specifically, the "Get Attachments" operation under the "Attachments" resource allows users to retrieve attachment files associated with customers. It supports fetching either all attachments or those linked to a specific customer.

Common scenarios include:

  • Downloading all attachments for backup or audit purposes.
  • Retrieving attachments related to a particular customer for review or processing.
  • Automating workflows that require access to invoice or document attachments stored in Easybill.

Practical example:

  • A user wants to fetch all invoice attachments for a given customer to send them via email automatically.
  • Another use case is retrieving all attachments in bulk to sync with an external document management system.

Properties

Name Meaning
Retrieve All Attachments Boolean option to fetch all available attachments instead of filtering by a specific customer.
Customer Select a specific customer to retrieve attachments for. Can be chosen from a list or by ID (numeric).
Limit Limits the number of attachments returned. Default is 100, maximum allowed is 1000.

Output

The node outputs a JSON array where each item represents an attachment object retrieved from Easybill. Each attachment object typically contains metadata such as attachment ID, file name, and other relevant details provided by the Easybill API.

If binary data is included (not explicitly shown in the code), it would represent the actual content of the attachment files, allowing further processing like saving or forwarding.

Dependencies

  • Requires an active Easybill API credential configured in n8n to authenticate requests.
  • Relies on internal helper functions and endpoint handlers bundled within the node's codebase to communicate with the Easybill API.
  • No additional external dependencies are indicated beyond the Easybill API access.

Troubleshooting

  • Invalid Customer ID: If the customer ID is not numeric, the node will reject it due to regex validation. Ensure the ID consists only of digits.
  • API Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify the API key/token is correctly set up in n8n credentials.
  • Limit Exceeded: Setting the limit above 1000 will be rejected. Use a value between 1 and 1000.
  • Empty Results: If no attachments are found, ensure the correct customer is selected or try enabling "Retrieve All Attachments" to broaden the search.
  • Network Issues: Connectivity problems with the Easybill API can cause request failures. Check network settings and API availability.

Links and References

Discussion