Actions80
- 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
- Todos Actions
Overview
This node updates an existing document within a specified bucket in the Basecamp service. It is useful when you need to modify the title or content of a document that already exists in your project management environment. For example, you might use this node to correct information, add new details, or update the formatting of a project document without creating a new one.
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 the Rich text guide. |
Output
The node outputs JSON data representing the updated document as returned by the Basecamp API. This typically includes fields such as the document's ID, updated title, content, timestamps, and other metadata reflecting the current state after the update operation.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Basecamp.
- The node uses the Basecamp API endpoint specific to the authenticated user's account.
- Proper permissions on the Basecamp project and bucket are necessary to perform document updates.
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: Ensure the OAuth2 credentials are valid and have not expired.
- HTML Content Issues: Invalid or unsupported HTML tags in the content may cause the update to fail or render incorrectly. Follow the Rich text guide for allowed tags.
- Empty Required Fields: Bucket Id and Document Id are mandatory; missing these will prevent execution.