Actions109
- 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
- Lists Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Users Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Websites Actions
Overview
This node is designed to retrieve details of a specific upload by its unique identifier. It is useful in scenarios where you need to fetch metadata or information about a particular uploaded file or resource within a system that manages uploads. For example, after uploading a file, you might want to get its status, size, or other attributes by providing its ID.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the requested upload. This is required to specify which upload's details to retrieve. |
Output
The node outputs JSON data containing the details of the requested upload identified by the provided ID. The exact structure depends on the API response but typically includes metadata such as upload status, filename, size, timestamps, and possibly URLs or references to the uploaded content.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication with the external service managing uploads.
- The node uses a base URL configured via credentials to connect to the appropriate API endpoint.
- The underlying implementation relies on an OpenAPI specification bundled with the node for request construction.
Troubleshooting
- Invalid or missing ID: If the provided upload ID does not exist or is invalid, the node may return an error indicating the upload was not found. Ensure the ID is correct and exists in the system.
- Authentication errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key or token is correctly set up in the node credentials.
- Network issues: Connectivity problems to the API endpoint can result in timeouts or connection errors. Check network access and base URL configuration.
- Unexpected response format: If the API changes its response schema, the node might fail to parse the output correctly. Updating the node or its OpenAPI spec may be necessary.
Links and References
- Refer to the external service’s API documentation for detailed information on the upload resource and its fields.
- Consult n8n documentation on how to configure API credentials and use custom nodes.