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 allows you to create a new chatbot within the Basecamp platform. It is useful for automating interactions in Basecamp chats by defining a chatbot that can respond to commands or queries. For example, you might use this node to set up a custom bot that listens for specific keywords or commands in a chat and triggers workflows or external services accordingly.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the Basecamp bucket (project area) where the chatbot will be created. |
| Chat Id | The numeric identifier of the chat within the specified bucket where the chatbot will operate. |
| Service Name | The name of the chatbot used to invoke queries and commands. Must contain no spaces, emojis, or non-word characters. |
| Command Url | The HTTPS URL that Basecamp will call when the chatbot is addressed. This URL handles incoming commands or queries. |
Output
The node outputs JSON data representing the newly created chatbot object as returned by the Basecamp API. This typically includes details such as the chatbot's ID, service name, associated bucket and chat IDs, and the command URL. There is no binary output.
Dependencies
- Requires an active Basecamp account with appropriate permissions.
- Needs an API authentication token configured in n8n credentials to authorize requests to the Basecamp API.
- The node uses the Basecamp API endpoint
https://3.basecampapi.com/combined with the user's Basecamp ID.
Troubleshooting
- Invalid Service Name: If the service name contains spaces, emojis, or special characters, the API may reject the request. Ensure the service name only contains word characters.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key/token is correctly set up in n8n.
- Incorrect Bucket or Chat IDs: Providing non-existent or unauthorized bucket/chat IDs will result in errors. Confirm these IDs are valid and accessible.
- Command URL Issues: The command URL must be a valid HTTPS URL reachable by Basecamp. Invalid URLs or unreachable endpoints will cause failures.