Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation allows uploading a file and associating it with a specific record in an external system. It is useful when you need to attach documents, images, or other files to entities such as assets, websites, procedures, passwords, companies, or articles within that system.
Typical use cases include:
- Uploading a contract PDF to a company record.
- Attaching an image file to an asset or website entry.
- Adding documentation files to procedures or articles.
By automating this upload process, users can streamline file management and ensure relevant files are properly linked to their corresponding records.
Properties
Name | Meaning |
---|---|
File | The file to upload. This should be provided as binary data from the workflow input. |
Upload Uploadable Id | Numeric ID of the record to which the uploaded file will be attached. |
Upload Uploadable Type | Type of the record to attach the file to. Options include: Asset, Website, Procedure, AssetPassword, Company, Article |
Output
The node outputs JSON data representing the response from the upload API call. This typically includes metadata about the uploaded file and its association with the specified record.
If the node supports binary data output (not explicitly shown here), it would represent the uploaded file or related binary content. However, based on the provided code and properties, the main output is JSON confirming the upload result.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to authorize requests to the external service.
- The base URL for the API must be set in the node's credential configuration.
- The node depends on the external service's API endpoint that handles file uploads and associations.
Troubleshooting
- File not uploading: Ensure the file property contains valid binary data and is correctly referenced in the workflow.
- Invalid record ID or type: Verify that the
uploadable_id
corresponds to an existing record and thatuploadable_type
matches one of the supported types. - Authentication errors: Confirm that the API credentials are correctly configured and have sufficient permissions.
- API errors: Check the response message for details; common issues include exceeding file size limits or unsupported file formats.
Links and References
- Refer to the external service’s API documentation for detailed information on file upload endpoints and required parameters.
- Consult n8n documentation on handling binary data and configuring credentials for API authentication.