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 within a vault. This is useful for workflows that need to access or process files stored in Basecamp, such as automating file downloads, backups, or integrating uploaded content into other systems.
Practical examples include:
- Automatically retrieving all files uploaded to a project’s document bucket for processing.
- Syncing files from Basecamp storage to another cloud service.
- Triggering notifications or further actions when new uploads appear in a specific bucket.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket from which to retrieve uploads. |
| Vault Id | The numeric identifier of the vault containing the bucket where uploads are stored. |
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, size, URL, and other relevant attributes provided by the Basecamp API.
If the node supports binary data output (not explicitly shown in the code), it would represent the actual file contents of the uploads. However, based on the static analysis, the output primarily consists of JSON metadata about the uploads.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node depends on the Basecamp API endpoint structured as
https://3.basecampapi.com/{basecampId}. - Proper configuration of the API credentials and permissions to access the specified vault and bucket is necessary.
Troubleshooting
- Invalid Bucket or Vault Id: If the provided IDs do not exist or the authenticated user lacks access, the API will return errors. Verify the IDs and permissions.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly configured.
- Empty Results: If no uploads are found, confirm that the bucket and vault contain files and that the IDs are correct.
- API Rate Limits: Excessive requests may lead to rate limiting; implement retries or backoff strategies if needed.
Links and References
- Basecamp API Documentation
- n8n Documentation on Creating Custom Nodes
- Basecamp Uploads API Reference (for detailed upload object structure)