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
This node interacts with the Basecamp API to retrieve uploads from a specified storage location. Specifically, the "Get Uploads" operation under the "Uploads" resource fetches files stored in a particular bucket and vault within Basecamp. This is useful for workflows that need to access or process files stored in Basecamp, such as automating file downloads, backups, or integrating Basecamp files into other systems.
Practical examples include:
- Automatically retrieving all files uploaded to a project’s designated bucket for further processing.
- Syncing files from Basecamp to cloud storage or other collaboration tools.
- Triggering notifications or actions based on newly uploaded files.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket (storage container) from which to get uploads. |
| Vault Id | The numeric identifier of the vault (a higher-level container or folder) containing the bucket. |
Both properties are required and must be provided as numbers.
Output
The node outputs JSON data representing the list of uploads retrieved from the specified bucket and vault. Each item in the output typically contains metadata about an upload, such as its ID, name, URL, size, and possibly timestamps or uploader information.
If the node supports binary data output (not explicitly shown here), it would represent the actual file content of the uploads. However, based on the code snippet, the primary output is structured JSON metadata about the uploads.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node depends on the Basecamp API being accessible and the user having appropriate permissions to access the specified bucket and vault.
- No additional external dependencies beyond the Basecamp API and its authentication are indicated.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Vault Id will cause the request to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Network connectivity problems may prevent reaching the Basecamp API endpoint.
Error messages:
- Authorization errors typically indicate invalid or expired API tokens; re-authenticate or update credentials.
- "Not Found" errors may mean the specified bucket or vault IDs do not exist or are inaccessible.
- Rate limiting errors from the API require waiting before retrying or adjusting request frequency.
Links and References
- Basecamp API Documentation
- n8n documentation on creating custom nodes