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 you to update an existing chatbot integration within a Basecamp project. It is useful when you want to modify the configuration of a chatbot, such as changing its service name or the URL that Basecamp calls when the bot is addressed. This can help automate and customize interactions in your Basecamp chats by updating how the chatbot behaves or connects to external services.
Practical examples:
- Changing the command URL of a chatbot to point to a new webhook endpoint after migrating your backend.
- Renaming the chatbot service to better reflect its purpose or to comply with naming conventions.
- Updating chatbot settings programmatically as part of a deployment or configuration management workflow.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the Basecamp project (bucket) where the chatbot exists. Used in the API endpoint path. |
| chatId | The numeric ID of the chat or campfire within the project. Used in the API endpoint path. |
| integrationId | The numeric ID of the chatbot/integration to update. Used in the API endpoint path. |
| Service Name | The new name for the chatbot service. Must be a string without spaces, emojis, or non-word characters. |
| Chatbot Fields | Contains fields to update on the chatbot. Currently supports: |
| - Command URL | The HTTPS URL that Basecamp should call when the bot is addressed. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the body. |
Output
The node outputs JSON data representing the response from the Basecamp API after updating the chatbot. By default, it returns only the response body, which typically contains the updated chatbot details or confirmation of the update.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, including status code, headers, and body, allowing for more detailed handling or debugging.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- Network access to Basecamp's API endpoints is necessary.
Troubleshooting
- Invalid IDs: Ensure that the Project ID, chatId, and integrationId are correct and correspond to existing resources in Basecamp; otherwise, the API will return errors like 404 Not Found.
- Invalid Service Name: The service name must not contain spaces, emojis, or special characters. Violating this may cause validation errors.
- Command URL Issues: The Command URL must be a valid HTTPS URL. Providing an invalid URL may result in API rejection.
- Authentication Errors: If the OAuth2 credentials are missing or expired, the node will fail to authenticate with Basecamp.
- API Rate Limits: Frequent updates might hit Basecamp API rate limits, causing temporary failures.
- Return Full Response Misuse: Enabling "Return Full Response" changes the output format; downstream nodes expecting only the body might break if not adjusted accordingly.