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 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's file storage system.
Practical examples include:
- Automatically retrieving newly uploaded files for processing or backup.
- Integrating Basecamp file storage with other services by fetching files and then sending them elsewhere.
- Monitoring file changes or updates in specific buckets for audit or notification purposes.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket from which to retrieve uploads (required). |
| Vault Id | The numeric identifier of the vault containing the bucket (required). |
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, creation date, and possibly other relevant details depending on the Basecamp API response.
If binary data is included (e.g., file contents), it would be represented in the binary property of the output items, but based on the provided code snippet, the focus is on JSON metadata retrieval.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node depends on the Basecamp API endpoint
https://3.basecampapi.com/combined with the user's Basecamp account ID. - The user must configure the node with valid credentials and have appropriate permissions to access the specified vault and bucket.
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: Ensure the API key or OAuth token is valid and has not expired.
- Network Issues: Connectivity problems can cause request failures; check network settings.
- Empty Results: If no uploads are returned, confirm that the bucket actually contains files.
Common error messages might include unauthorized access, resource not found, or rate limiting. Resolving these involves checking credentials, verifying resource identifiers, and respecting API usage limits.