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
The "Update Document" operation in the Documents resource allows users to modify an existing document within a specified bucket. This node is useful when you need to programmatically update the title or content of documents stored in a Basecamp project, such as revising meeting notes, updating project documentation, or correcting information without manually accessing the Basecamp interface.
Practical examples include:
- Automatically updating project documentation after changes in source data.
- Editing meeting minutes with additional notes or corrections.
- Synchronizing document content from other systems or databases.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket (folder) where the document resides. |
| Document Id | The numeric identifier of the document to be updated. |
| Title | The new title for the document. |
| Content | The new body content of the document in HTML format. Allowed HTML tags follow Basecamp's rich text guide. |
Output
The node outputs JSON data representing the updated document object returned by the Basecamp API. This typically includes fields such as the document's ID, updated title, content, timestamps, and metadata confirming the successful update.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses the Basecamp API endpoint constructed with the user's Basecamp account ID.
Troubleshooting
- Invalid Bucket or Document Id: If the provided IDs do not exist or are incorrect, the API will return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n.
- HTML Content Issues: Providing unsupported HTML tags or malformed content in the "Content" property may result in API rejection or unexpected rendering. Follow Basecamp's rich text guidelines.
- Empty Required Fields: Omitting required fields like Bucket Id or Document Id will prevent the request from being sent. Make sure all mandatory inputs are provided.