Actions80
- Todos Actions
- 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
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 (used for invocation), and the command URL that Basecamp calls when the bot is addressed.
Typical use cases include:
- Changing the chatbot’s command endpoint URL after deployment changes.
- Renaming the chatbot service to reflect updated functionality or branding.
- Reassigning the chatbot to a different chat or bucket within Basecamp.
For example, if you have a chatbot integrated with Basecamp that listens for commands, but you need to update the webhook URL it calls or rename the bot for clarity, this operation facilitates those updates seamlessly.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket where the chatbot resides. |
| Chat Id | Numeric identifier of the chat associated with the chatbot. |
| Integration Id | Numeric identifier of the integration linked to the chatbot. |
| Service Name | The chatbot’s invocation name; must be a string without spaces, emojis, or non-word characters. |
| Command Url | HTTPS URL endpoint that Basecamp will call when the chatbot is triggered by user commands or queries. |
Output
The node outputs JSON data representing the updated chatbot object as returned by the Basecamp API. This typically includes the chatbot’s current configuration details such as IDs, service name, command URL, and other metadata confirming the successful update.
No binary data output is involved in this operation.
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 special characters, the API may reject the request. 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 non-existent or incorrect bucket, chat, or integration IDs will result in errors. Double-check these numeric values before running the node.
- Invalid Command URL: The command URL must be a valid HTTPS URL. Using HTTP or malformed URLs can cause request failures.
Links and References
- Basecamp API Documentation – Official API docs for managing chatbots and integrations.
- n8n Documentation – General guidance on setting up credentials and using HTTP request nodes.