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 allows you to create a new chatbot message line in a specified chat within a Basecamp project. It is useful for automating communication by programmatically sending messages to chatbots integrated into Basecamp chats. Typical use cases include posting notifications, alerts, or updates directly into team chatrooms managed by Basecamp chatbots.
For example, you might use this node to send a formatted message with rich text and tables to a project chat whenever a deployment completes or an error occurs, enabling your team to stay informed without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Chatbot Key | The unique key identifying the chatbot to which the message line will be sent. |
| Bucket Id | The numeric identifier of the Basecamp project (bucket) containing the chat. |
| Chat Id | The numeric identifier of the specific chat within the bucket where the chatbot line will be created. |
| Content Param | Optional. Allows modifying the name of the content parameter in the query string to support third-party webhooks. |
| Content | The body of the chatbot message line. Supports rich text HTML tags plus additional tags like table, tr, td, th, thead, tbody, details, summary. |
Output
The node outputs JSON data representing the newly created chatbot line as returned by the Basecamp API. This typically includes details such as the message ID, content, timestamps, and metadata about the chatbot line. There is no binary output.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically based on the authenticated user's Basecamp account ID.
- No other external dependencies are required.
Troubleshooting
- Invalid Credentials or Unauthorized: If the API key or OAuth token is invalid or expired, the node will fail with an authorization error. Ensure the credentials are correctly set up and have sufficient permissions.
- Incorrect Bucket or Chat IDs: Providing wrong numeric IDs for bucket or chat will result in "not found" errors. Verify these IDs exist in your Basecamp account.
- Malformed Content: Since the content supports rich HTML and custom tags, malformed or unsupported markup may cause the API to reject the request. Validate the content format before sending.
- Missing Required Parameters: Omitting required fields like Chatbot Key, Bucket Id, Chat Id, or Content will cause validation errors. Make sure all required inputs are provided.