Actions80
- 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
- Todos Actions
Overview
The "Create Upload" operation under the "Uploads" resource allows users to create a new file upload within a specified bucket and vault. This node is useful for automating the process of attaching files or documents to projects, tasks, or other entities managed in the system. For example, you could use this node to programmatically upload images, reports, or attachments related to project management workflows.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket where the upload will be stored. |
| Vault Id | Numeric identifier of the vault associated with the upload. |
| Attachable Sgid | A string representing the SGID (Secure Global ID) for the uploaded attachment. |
| Description | Optional HTML-formatted information describing the upload. |
| Base Name | The new filename for the upload without its extension (e.g., "pizza" for "pizza.png"). |
Output
The node outputs JSON data representing the result of the upload creation. This typically includes metadata about the newly created upload such as its ID, URLs, timestamps, and any other relevant details returned by the API. There is no indication that binary data is output directly by this node; it focuses on metadata about the upload.
Dependencies
- Requires an API key credential for authentication with the external service.
- The node uses a base URL constructed dynamically from credentials.
- No additional external dependencies are indicated beyond the API access.
Troubleshooting
- Missing Required Fields: Ensure that
Bucket Id,Vault Id, andAttachable Sgidare provided, as they are mandatory. - Invalid SGID: If the
Attachable Sgidis incorrect or expired, the upload may fail. Verify the SGID format and validity. - API Authentication Errors: Confirm that the API key or token used is valid and has sufficient permissions.
- Network Issues: Check connectivity to the API endpoint if requests time out or fail.
- File Naming Conflicts: If the
Base Nameconflicts with existing files, the API might reject the upload or overwrite files depending on backend behavior.
Links and References
- Refer to the official API documentation of the service managing uploads for detailed field descriptions and examples.
- Consult n8n documentation on how to configure API credentials and handle file uploads.