Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Cards Actions
- Suppliers Actions
- Fund Accounts Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation allows uploading a file to be used as a custom field source for suppliers. It is useful when you want to import or update supplier-related data in bulk by providing a file that contains the necessary information. For example, if your supplier management system supports custom fields populated from external files, this operation facilitates automating that upload process within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the file upload applies |
Output
The node outputs JSON data representing the result of the file upload operation. This typically includes confirmation details such as success status, any identifiers related to the uploaded file, or error messages if the upload failed. The output does not explicitly mention binary data handling, so it is assumed the file content is handled internally and only metadata or response info is returned in JSON format.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on an external service endpoint (base URL provided via credentials) that accepts file uploads for supplier custom fields.
- The node uses an OpenAPI-based client internally to interact with the external API.
Troubleshooting
- Common issues:
- Missing or invalid Account Id property will cause the operation to fail.
- Authentication errors if the API key or credentials are not set up correctly.
- Network or endpoint errors if the external service is unreachable or misconfigured.
- Error messages:
- "Account Id is required" – Ensure the Account Id input is provided.
- "Authentication failed" – Verify API credentials and permissions.
- "File upload failed" – Check file format, size limits, and API endpoint availability.
Links and References
- Refer to the external supplier management system's API documentation for details on file formats and custom field requirements.
- n8n documentation on how to configure API credentials and use HTTP request nodes for file uploads.