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 integrates with the Basecamp API to create a new upload within a specified project and vault. It is useful for automating file uploads linked to attachments in Basecamp projects, enabling workflows that require programmatic management of project files and documentation.
Typical use cases include:
- Automatically uploading generated reports or documents to a Basecamp project.
- Attaching files received from other systems or users into specific vaults within Basecamp.
- Enhancing project collaboration by programmatically adding relevant files with descriptions.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the upload will be created. Used in the API path. |
| Vault ID | The numeric ID of the vault within the project where the upload will be stored. Used in the API path. |
| Attachment SGID | The Secure Global ID (SGID) string representing the attachment to upload. Obtained from a prior attachment creation step. |
| Description | Optional textual description of the upload; can contain HTML content to describe the file. |
| Base Filename | Optional new base filename (without extension) to assign to the uploaded file. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the response from the Basecamp API after creating the upload. This typically includes details about the newly created upload such as its ID, URLs, metadata, and status.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, including status code and headers, which can be useful for debugging or advanced handling.
The node does not output binary data directly; it handles metadata and references related to the uploaded attachment.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The user must provide valid credentials with appropriate permissions to access the specified project and vault.
- The node depends on the Basecamp API endpoints for managing uploads and attachments.
Troubleshooting
- Invalid Project or Vault ID: Ensure the provided numeric IDs correspond to existing projects and vaults accessible by the authenticated user.
- Attachment SGID Issues: The attachment SGID must be obtained from a successful attachment creation call; invalid or expired SGIDs will cause errors.
- Permission Errors: Insufficient permissions or incorrect OAuth scopes may result in authorization failures.
- API Rate Limits: Hitting Basecamp API rate limits can cause request failures; implement retries or backoff strategies if needed.
- Return Full Response Misuse: Enabling full response output changes the structure of the output; downstream nodes expecting only the body may fail unless adjusted.
Links and References
- Basecamp API Documentation
- Basecamp Uploads API Reference
- n8n OAuth2 Credential Setup Guide (generic link to n8n docs on OAuth2)