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 a specific upload within a project (referred to as a "bucket" in the API). The "Get an Upload" operation fetches details of an upload by its unique ID within a specified project. This is useful when you want to programmatically access metadata or information about files or uploads stored in a Basecamp project.
Common scenarios:
- Automating retrieval of file metadata for reporting or auditing.
- Integrating Basecamp uploads into other workflows, such as syncing files or triggering notifications based on upload details.
- Fetching upload details to display or process them in downstream automation steps.
Example:
You have a project with ID 12345 and want to get details about an upload with ID 67890. Using this node operation, you provide these IDs, and it returns the upload's metadata such as filename, size, URL, and other relevant info.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the upload resides. Used in the API endpoint path. |
| Upload ID | The numeric ID of the upload to retrieve. Used in the API endpoint path. |
| Return Full Response | Boolean option to return the entire HTTP response including status code and headers instead of just the response body. |
Output
The node outputs JSON data representing the upload's details retrieved from the Basecamp API. This typically includes metadata fields such as:
- Upload ID
- Filename
- Content type
- Size
- URLs or download links
- Creation and modification timestamps
- Associated project or bucket information
If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing status code, headers, and body.
The node does not output binary data; it only returns JSON metadata about the upload.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The user must configure the node with valid credentials that allow access to the target Basecamp account.
- The node uses the Basecamp API base URL constructed dynamically from the authenticated account ID.
Troubleshooting
- Invalid Project or Upload ID: If either ID is incorrect or does not exist, the API will return an error (e.g., 404 Not Found). Verify the IDs are correct and accessible with your credentials.
- Authentication Errors: Ensure the OAuth2 credentials are valid and have sufficient permissions to read uploads in the specified project.
- Network Issues: Connectivity problems can cause request failures. Check network access and Basecamp service status.
- Return Full Response Confusion: When enabling "Return Full Response," the output structure changes. Make sure downstream nodes handle the full response object accordingly.