Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node operation allows you to create a new upload in a specified storage context by providing details such as the bucket and vault identifiers, an attachable SGID (a secure global identifier for attachments), and optional metadata like description and base file name. It is useful when automating file uploads to a remote service or system that organizes files into buckets and vaults, enabling integration with workflows that require managing digital assets or documents.
Practical examples include:
- Uploading user-generated content to a cloud storage bucket within a workflow.
- Attaching files programmatically to project management or collaboration tools.
- Automating backup of files with descriptive metadata for easier retrieval.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the target bucket where the upload will be stored. |
| Vault Id | Numeric identifier of the vault associated with the upload, representing a storage area. |
| Attachable Sgid | A required string representing the secure global identifier for the uploaded attachment. |
| Description | Optional HTML-formatted string describing the upload, providing additional information. |
| Base Name | Optional new file name without extension for the upload (e.g., "pizza" for "pizza.png"). |
Output
The node outputs JSON data representing the result of the upload creation request. This typically includes details about the newly created upload such as its ID, status, and any metadata returned by the API. The output does not explicitly mention binary data handling, so it is assumed to focus on JSON metadata about the upload.
Dependencies
- Requires an API key credential or OAuth2 token configured in n8n to authenticate requests to the external service managing uploads.
- The node depends on the external API endpoint that handles upload creation, which expects parameters like bucket ID, vault ID, and attachable SGID.
- Proper configuration of base URL and authentication headers is necessary for successful communication.
Troubleshooting
- Missing Required Fields: Errors may occur if mandatory fields like Bucket Id, Vault Id, or Attachable Sgid are not provided. Ensure these inputs are correctly set.
- Authentication Failures: If the API key or token is invalid or missing, the node will fail to authenticate. Verify credentials in n8n settings.
- Invalid Identifiers: Providing non-existent bucket or vault IDs can cause errors. Confirm these IDs exist and are accessible.
- Malformed Description or Base Name: Although optional, ensure that the description is valid HTML if used, and base name does not contain invalid characters.
- API Rate Limits or Network Issues: Temporary failures might happen due to rate limiting or connectivity problems; retrying after some time may help.
Links and References
- Refer to the external service’s API documentation for detailed information on upload creation endpoints and parameter requirements.
- Consult n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.