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
- 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 attach or import external data files that define or update supplier-specific custom fields in your workflow. For example, you might upload a CSV or JSON file containing supplier metadata that will then be processed or stored as part of the supplier's profile.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account associated with the supplier. This is a required string input. |
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 custom field source created or updated. If the node supports binary data output (e.g., returning the uploaded file or a processed version), it would be summarized here, but based on the provided code and properties, the main output is JSON confirming the upload.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on an external API endpoint (likely the supplier management system) to handle the file upload and associate it with the specified account.
- The base URL and headers for API requests are expected to be set up in the node credentials or configuration.
Troubleshooting
- Missing Account Id: Since "Account Id" is required, omitting it will cause errors. Ensure this property is always provided.
- Authentication Errors: If the API key or authentication token is invalid or missing, the upload will fail. Verify credentials are correctly configured.
- File Format Issues: Uploading unsupported file types or malformed files may cause the API to reject the upload. Confirm the file format matches the expected schema.
- Network or API Endpoint Errors: Connectivity issues or incorrect base URLs can prevent successful uploads. Check network access and API endpoint correctness.
Links and References
- Refer to your supplier management system’s API documentation for details on file upload endpoints and accepted file formats.
- Consult n8n documentation on how to configure API credentials and use HTTP request nodes if further customization is needed.