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
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 webhooks from third-party services. |
| 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.
If binary data were supported, it would represent attachments or media related to the chatbot line, but this operation focuses on textual content only.
Dependencies
- Requires an API authentication token or API key credential configured in n8n to authorize requests to the chatbot service.
- The node depends on the Basecamp API endpoint structure, specifically targeting chat and bucket identifiers.
- Proper configuration of the base URL and headers for JSON content-type is necessary.
Troubleshooting
- Missing or invalid Chatbot Key: Ensure the chatbot key is correctly provided and corresponds to an existing chatbot.
- Invalid Bucket Id or Chat Id: Verify that the numeric IDs are correct and that the user has access rights to these resources.
- Content formatting errors: If the content includes unsupported HTML tags or malformed markup, the API may reject the request. Use only supported tags as described.
- Authentication failures: Check that the API credentials are valid and have not expired.
- Network or API errors: Confirm network connectivity and that the Basecamp API service is operational.
Common error messages might include unauthorized access, resource not found, or validation errors on the content field. Resolving these usually involves verifying input parameters and credentials.
Links and References
- Basecamp API Documentation
- n8n Documentation on Creating Custom Nodes
- HTML tags supported in chatbot content: standard HTML5 tags plus
table,tr,td,th,thead,tbody,details,summary.