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 interacts with the Basecamp API to update an existing message within a specified project (referred to as a "bucket" in Basecamp). It allows users to modify key attributes of a message such as its subject, content, and category. This is useful for scenarios where messages need to be corrected, updated with new information, or re-categorized after their initial creation.
Practical examples include:
- Updating the title and body of a project announcement.
- Changing the category/type of a message to better reflect its purpose.
- Correcting typos or adding additional details to an existing message.
Properties
Name | Meaning |
---|---|
Project ID | The numeric ID of the project (bucket) where the message resides; used in the API endpoint path. |
messageId | The numeric ID of the message to update; used in the API endpoint path. |
Subject | The new title of the message. |
Message Fields | Additional fields to update on the message: |
- Content | The body of the message, which may contain HTML formatting. |
- Category ID | The numeric ID representing the message's type or category. |
Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the updated message object returned by the Basecamp API. If the "Return Full Response" option is enabled, the output will include the entire HTTP response including status code and headers, otherwise only the response body 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 message IDs that exist in the Basecamp account.
- Proper API permissions are necessary to update messages within the specified project.
Troubleshooting
- Invalid Project or Message ID: Errors may occur if the provided project or message 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.
- Validation Errors: Missing required fields like Subject or invalid field formats can cause the API to reject the request. Make sure all required inputs are provided and correctly formatted.
- API Rate Limits: Frequent updates might hit Basecamp API rate limits; handle such errors by retrying after some delay.