Actions76
- 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
Overview
This node integrates with the Basecamp API to create a new document within a specified project and vault. It is useful for automating documentation workflows, such as generating reports, meeting notes, or any content that needs to be stored and managed inside Basecamp projects. For example, you can use this node to programmatically add project documentation after a build process or to archive important communications automatically.
Properties
Name | Meaning |
---|---|
Project ID | The numeric ID of the project (bucket) where the document will be created. |
vaultId | The numeric ID of the vault within the project where the document will be stored. |
Title | The title of the document to be created. |
Content | The HTML content of the document. Can include formatted text and HTML elements. |
Status | Optional status field; set to "active" to publish the document immediately. |
Return Full Response | Boolean flag indicating whether to return the full HTTP response (status, headers, body) or just the response body. |
Output
The node outputs JSON data representing the newly created document or the full HTTP response if requested. The JSON typically includes details such as the document's ID, title, content, creation timestamps, and other metadata returned by the Basecamp API.
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.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects valid project and vault IDs to construct the API endpoint path.
- Proper API credentials must be configured in n8n to authorize requests.
Troubleshooting
- Invalid Project or Vault ID: If the provided IDs do not exist or are incorrect, the API will return an error. Verify the IDs in your Basecamp account.
- Authentication Errors: Ensure that the OAuth2 credentials are correctly set up and have sufficient permissions to create documents.
- Missing Required Fields: Title and Content are mandatory. Omitting them will cause the request to fail.
- Status Field Usage: Setting the status incorrectly may prevent the document from being published as expected. Use "active" to publish immediately.
- API Rate Limits: Frequent calls might hit Basecamp API rate limits; handle errors accordingly.