Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
Overview
This node operation updates an existing document within a specified bucket in the Basecamp service. It allows users to modify the title and content of a document identified by its unique document ID and bucket ID. This is useful for workflows that need to programmatically maintain or revise project documentation, meeting notes, or any other stored documents in Basecamp.
Practical examples include:
- Automatically updating project documentation after changes in a source system.
- Modifying meeting notes with additional information collected from other tools.
- Correcting or appending content in documents as part of a review process.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket containing the document to update. |
| Document Id | Numeric identifier of the document to be updated. |
| Title | New title for the document. |
| Content | 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 possibly metadata about the document's state after the update.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token configured in n8n credentials to access the Basecamp API.
- The node uses the Basecamp API endpoint specific to the user's Basecamp account (base URL constructed using the Basecamp account ID).
- Proper permissions on the Basecamp account to update documents are necessary.
Troubleshooting
- Invalid Bucket or Document ID: If the provided IDs do not exist or the user lacks access, the API will return an error. Verify the IDs and permissions.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key/token is correctly set up.
- HTML Content Issues: Providing unsupported HTML tags or malformed content may cause the API to reject the update. Follow Basecamp's rich text guidelines.
- Empty Required Fields: Bucket Id and Document Id are required; missing these will prevent execution.