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
The "Create Chatbot Line" operation in the Chatbots resource allows users to send a new message line to a chatbot conversation. This is useful for automating interactions with chatbots by programmatically adding content lines, such as notifications, updates, or responses, into an ongoing chat session.
Practical examples include:
- Automatically posting status updates or alerts from external systems into a chatbot conversation.
- Sending formatted messages with rich text or HTML content to enhance readability and presentation within the chatbot.
- Integrating third-party webhook services that trigger chatbot messages dynamically.
Properties
| Name | Meaning |
|---|---|
| Chatbot Key | A unique string key identifying the target chatbot where the line will be created. |
| Bucket Id | Numeric identifier of the bucket (a container or grouping) within which the chat exists. |
| Chat Id | Numeric identifier of the specific chat session to which the line will be added. |
| Content Param | Optional string to modify the name of the required content parameter, supporting integration with third-party webhooks. |
| Content | The main body of the chatbot line. Supports rich text HTML tags plus additional tags like table, tr, td, th, thead, tbody, details, summary for enhanced formatting. |
Output
The node outputs JSON data representing the response from the API after creating the chatbot line. This typically includes details about the newly created line such as its ID, content, timestamps, and any metadata returned by the service.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token or API key credential configured in n8n to authorize requests to the Basecamp API.
- The node depends on the Basecamp API endpoint structured as
https://3.basecampapi.com/{basecampId}where{basecampId}is provided via credentials. - The node uses HTTP headers specifying JSON content type and accepts JSON responses.
Troubleshooting
- Missing or invalid Chatbot Key, Bucket Id, or Chat Id: Ensure these identifiers are correct and correspond to existing resources in your Basecamp account.
- Authentication errors: Verify that the API key or OAuth2 credentials are correctly set up and have sufficient permissions.
- Content formatting issues: If the content contains unsupported HTML tags or malformed markup, the API may reject the request. Validate the content format before sending.
- Network or API errors: Check connectivity and Basecamp API status if requests fail unexpectedly.