Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts 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
- Suppliers Actions
- Fund Accounts Actions
- Cards 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 source for a custom field related to suppliers. It is useful when you want to import or update supplier information in bulk by providing a file that contains the relevant data for a custom field. Typical scenarios include integrating supplier data from external systems, updating supplier attributes en masse, or automating supplier data management workflows.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account associated with the supplier data upload |
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, and possibly metadata about the processed custom field source. 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 output.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on an external service API endpoint (likely the supplier management system) to accept the uploaded file and process it as a custom field source.
- The base URL for the API must be set in the node credentials or environment configuration.
Troubleshooting
- Common issues:
- Missing or invalid Account Id property will cause the operation to fail.
- Authentication errors if the API key or token is missing or incorrect.
- File format or size restrictions imposed by the external API might cause upload failures.
- Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Invalid Account Id": Verify the provided account identifier is correct and exists.
- "File upload failed": Ensure the file meets the required format and size limits.
Links and References
- Refer to the external supplier management system's API documentation for details on file upload requirements and custom field source formats.
- n8n documentation on how to configure API credentials and use file upload nodes.