Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
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.
- Sending formatted messages with rich text or HTML content to enhance chatbot conversations.
- Integrating third-party webhook data by customizing the content parameter name.
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 rename the required content parameter, enabling support for webhooks from third-party services. |
| Content | The main body of the chatbot line. Supports rich text HTML tags and 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 Basecamp API.
- The node uses the Basecamp API endpoint, specifically targeting the chat and bucket identifiers provided.
- Proper network access to the Basecamp API service is necessary.
Troubleshooting
- Invalid or missing 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 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. Use only supported tags as described.
- Webhook integration problems: When using
Content Paramto customize the content parameter name, ensure the external webhook sends data matching this custom name.
Common error messages might include unauthorized access, resource not found, or validation errors on the content field. Resolving them usually involves checking credentials, verifying IDs, and validating content format.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes
- HTML Supported Tags for Chat Content (general reference for allowed tags)