Actions119
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Overview
This node interacts with the Basecamp API to retrieve information about uploads within a specified project and vault. Specifically, the "Get Uploads" operation fetches all or a limited number of upload records associated with a given project (referred to as a bucket) and vault.
Common scenarios where this node is beneficial include:
- Automating the retrieval of files uploaded to a particular project for further processing or backup.
- Integrating Basecamp file uploads into workflows that require analysis, reporting, or synchronization with other systems.
- Monitoring new uploads in projects to trigger notifications or downstream actions.
For example, a user might configure this node to get all uploads from a specific project vault to generate a report on recent file activity or to sync those files with a cloud storage service.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket). Used in the API endpoint path to specify which project's uploads to retrieve. |
| Vault ID | The numeric ID of the vault within the project. Used in the API endpoint path to specify the vault containing uploads. |
| Return All Results | Boolean option to either return all available upload records or limit the results to a default or specified count. |
| Return Full Response | Boolean option to return the entire HTTP response including status code, headers, and body instead of just the response body. |
Output
The node outputs JSON data representing the uploads retrieved from the specified project vault. The structure typically includes an array of upload objects, each containing metadata such as upload ID, filename, size, creation date, and possibly URLs or references to the uploaded files.
If the "Return Full Response" property is enabled, the output will include the full HTTP response object, encompassing status code, headers, and the body with the uploads data.
The node does not output binary data directly; it only provides metadata and references related to the uploads.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to access project and vault data.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies are required beyond the Basecamp API and valid credentials.
Troubleshooting
- Invalid Project or Vault ID: If the provided project or vault ID does not exist or the authenticated user lacks access, the API may return errors or empty results. Verify IDs and permissions.
- Authentication Errors: Ensure the OAuth2 credentials are valid and have not expired. Re-authenticate if necessary.
- Pagination Issues: When "Return All Results" is enabled, the node handles pagination automatically. However, network issues or API rate limits could interrupt fetching all pages.
- API Rate Limits: Excessive requests may lead to rate limiting by Basecamp. Implement retry logic or reduce request frequency.
- Unexpected Response Structure: If the API changes, the node's parsing might fail. Check for updates to the node or API documentation.