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 for scenarios where you need to programmatically modify document content or metadata, such as updating project documentation, meeting notes, or any collaborative documents stored in Basecamp.
For example, you might use this node to:
- Change the title of a project specification document.
- Update the HTML content of a meeting summary after new information becomes available.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket (folder) containing the document to update. |
| Document Id | The numeric identifier of the document that you want to update. |
| Title | The new title for the document. |
| Content | The updated body 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 other metadata reflecting the current state after the update.
No binary data output is involved.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Basecamp.
- The node uses the Basecamp API endpoint specific to the user's Basecamp account, constructed using the Basecamp account ID from credentials.
- Network connectivity to Basecamp's API service is necessary.
Troubleshooting
- Invalid Bucket Id or Document Id: If these 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 expired OAuth2 tokens will cause authorization failures. Re-authenticate or refresh credentials as needed.
- HTML Content Issues: Providing invalid or unsupported HTML tags in the content may cause the API to reject the update. Ensure the content follows Basecamp's rich text guidelines.
- API Rate Limits: Frequent updates may hit rate limits imposed by Basecamp. Implement retry logic or reduce request frequency if errors occur.