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 operation updates an existing chatbot configuration in the Basecamp system. It allows users to modify key chatbot properties such as its associated bucket, chat, integration identifiers, the chatbot's service name, and the command URL that Basecamp calls when the bot is addressed.
Typical use cases include:
- Changing the chatbot’s invocation name to better reflect its purpose or branding.
- Updating the URL endpoint where chatbot commands are sent, for example, if the backend service handling chatbot commands has moved or changed.
- Adjusting the bucket, chat, or integration IDs to reorganize or reassign the chatbot within different parts of a Basecamp project.
Practical example: A team wants to rename their chatbot from "helpbot" to "assistbot" and update the webhook URL to a new server endpoint without recreating the chatbot from scratch.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket (project area) where the chatbot is located or assigned. |
| Chat Id | Numeric identifier of the specific chat within the bucket that the chatbot interacts with. |
| Integration Id | Numeric identifier of the integration instance related to the chatbot. |
| Service Name | The chatbot’s invocation name used to trigger queries and commands. Must be a string without spaces, emojis, or special characters. |
| Command Url | HTTPS URL endpoint that Basecamp calls when the chatbot is addressed; this is where chatbot commands are sent. |
Output
The node outputs JSON data representing the updated chatbot object as returned by the Basecamp API. This typically includes confirmation of the updated fields such as the chatbot’s ID, service name, command URL, and associated bucket/chat/integration IDs.
No binary data output is involved.
Dependencies
- Requires an active connection to the Basecamp API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is dynamically constructed using the Basecamp account ID from credentials.
Troubleshooting
- Invalid Service Name: If the service name contains spaces, emojis, or non-word characters, the API may reject the update. Ensure the service name follows the allowed pattern.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key/token is correctly set up in n8n.
- Incorrect IDs: Providing invalid bucket, chat, or integration IDs can result in not found errors. Double-check these numeric values correspond to existing resources.
- URL Format Issues: The command URL must be a valid HTTPS URL. Invalid URLs may cause request failures.
Links and References
- Basecamp API Documentation - For detailed API endpoints and data models related to chatbots.
- n8n Documentation - For general guidance on setting up credentials and using HTTP request nodes.