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 project chat and triggers workflows or notifications accordingly.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the Basecamp bucket (project folder) where the chatbot will be created. |
| Chat Id | Numeric identifier of the specific chat within the bucket where the chatbot will operate. |
| Service Name | The name of the chatbot used to invoke it via commands; must contain no spaces, emojis, or special characters. |
| Command Url | HTTPS URL endpoint that Basecamp will call when the chatbot is addressed, enabling command handling. |
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 API authentication token configured in n8n to access the Basecamp API.
- The node uses the Basecamp API base URL constructed dynamically from the user's credentials.
- No additional external dependencies beyond the Basecamp API and proper credential setup.
Troubleshooting
- Invalid Service Name: If the service name contains spaces, emojis, or non-word characters, the API may reject the request. Ensure the service name follows the allowed format.
- Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key or OAuth token is correctly configured.
- Invalid Bucket or Chat IDs: Providing non-existent or unauthorized bucket/chat IDs will result in errors. Confirm these IDs are correct and accessible with your credentials.
- Command URL Issues: The command URL must be a valid HTTPS endpoint reachable by Basecamp. Invalid URLs or unreachable endpoints may cause failures.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)