Actions13
- Customers Actions
- Documents Actions
- PDF-Templates Actions
- Attachments Actions
- Document-Payments Actions
Overview
This node integrates with the Easybill API to manage attachments related to documents or other resources within Easybill. Specifically, the "Create Attachments" operation allows users to upload binary data as attachments, optionally overriding the default filename. This is useful in scenarios where you want to programmatically add files such as invoices, receipts, or supporting documents to Easybill records.
Practical examples include:
- Automatically attaching scanned invoice PDFs to customer records.
- Uploading receipt images captured from a mobile app directly into Easybill.
- Adding supplementary documentation files to billing entries during automated workflows.
Properties
Name | Meaning |
---|---|
Binary Property | The name of the binary property that contains the file data to be uploaded (e.g., "data"). |
Override Filename | Optionally specify a custom filename to use instead of the default one when uploading. |
Output
The node outputs a JSON array containing the response(s) from the Easybill API after creating the attachment(s). Each item in the output corresponds to an attachment created and typically includes metadata about the uploaded file such as its ID, name, and associated resource information.
If the node handles binary data input, it does not output binary data itself but processes it for upload.
Dependencies
- Requires an active connection to the Easybill API via an API key credential configured in n8n.
- The node depends on internal helper functions and an API handler module to communicate with Easybill endpoints.
- Proper configuration of the binary property in the workflow is necessary to provide the file data.
Troubleshooting
Common issues:
- Incorrect binary property name: Ensure the binary property specified matches exactly the name of the binary data in the input.
- Missing or invalid API credentials: Verify that the API key credential is correctly set up and has sufficient permissions.
- Filename conflicts or invalid characters: When overriding filenames, ensure the name is valid and unique if required by Easybill.
Error messages:
- Authentication errors usually indicate invalid or missing API credentials.
- Validation errors may occur if the binary data is missing or improperly formatted.
- API rate limits or connectivity issues can cause request failures; check network and API status.
Links and References
- Easybill API Documentation (for detailed API endpoint info)
- n8n Documentation on Working with Binary Data
- n8n Credential Setup Guide (for configuring API keys)