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 allows updating an existing document within a specified project in Basecamp. It is useful when you need to modify the title or content of a document that already exists in a Basecamp project. Common scenarios include correcting information, adding new details, or revising documents collaboratively managed in Basecamp.
For example, if you have a project with documentation stored as Basecamp documents, this node can programmatically update those documents' titles and HTML content without manual intervention through the Basecamp UI.
Properties
Name | Meaning |
---|---|
Project ID | The numeric ID of the project (bucket) where the document resides. Used in API path. |
documentId | The numeric ID of the document to update. Used in API path. |
Title | The new title for the document. |
Content | The new content of the document, which may contain HTML markup. |
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 updated document as returned by the Basecamp API. If "Return Full Response" is enabled, the output includes the entire HTTP response object containing status code, headers, and body; otherwise, only the response body (the updated document data) is returned.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project and document IDs.
- Proper API permissions are necessary to update documents within the specified project.
Troubleshooting
- Invalid Project or Document ID: Errors may occur if the provided project or document ID does not exist or the authenticated user lacks access. Verify IDs and permissions.
- Authentication Errors: Ensure the OAuth2 credentials are correctly configured and have not expired.
- Content Validation: Since content supports HTML, malformed HTML might cause unexpected results. Validate HTML content before sending.
- API Rate Limits: Frequent updates may hit Basecamp API rate limits; handle such errors by implementing retries or backoff strategies.
Common error messages:
- 404 Not Found: The specified project or document ID does not exist.
- 401 Unauthorized: Authentication failed; check API credentials.
- 400 Bad Request: Invalid input data, e.g., missing required fields like title or content.