Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
This node integrates with the Basecamp API to create a new chatbot line within a specified chat (campfire) in a project. It allows users to post messages formatted in HTML, including tables and other rich content, directly into a chatbot conversation thread.
Common scenarios for this node include:
- Automating chatbot responses or announcements in Basecamp chats.
- Posting dynamic content generated by workflows into team discussions.
- Integrating external systems that send updates or notifications into Basecamp chatbots.
For example, a user could automate posting status updates or alerts from monitoring tools as chatbot lines in a project’s chatroom.
Properties
Name | Meaning |
---|---|
Chatbot Key | The unique key identifying the chatbot; used in the API endpoint path to specify which chatbot to post the line to. |
Project ID | The numeric ID of the Basecamp project (bucket) where the chat resides; used in the API endpoint path. |
chatId | The numeric ID of the chat (campfire) within the project where the chatbot line will be created; used in the API endpoint path. |
Content | The body of the chatbot line message. Supports HTML formatting including tags like <table> , <tr> , <td> . |
Content Parameter Name | Optional: changes the name of the 'content' parameter in the request query to support third-party webhook integrations. |
Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the response from the Basecamp API after creating the chatbot line. This typically includes details about the newly created chatbot line such as its ID, content, timestamps, and related metadata.
If "Return Full Response" is enabled, the output includes the entire HTTP response object, containing status code, headers, and body.
No binary data output is involved.
Dependencies
- Requires an authenticated connection to the Basecamp API using OAuth2 credentials.
- The node uses the Basecamp account ID from credentials to construct the API base URL.
- Proper permissions on the Basecamp project and chat are necessary to post chatbot lines.
Troubleshooting
- Invalid IDs: Errors may occur if the provided Project ID or chatId do not exist or the user lacks access. Verify these IDs and permissions.
- Authentication errors: Ensure the OAuth2 credentials are valid and have sufficient scopes to write chatbot lines.
- Malformed content: Since HTML is supported, invalid or unsafe HTML might cause API rejection. Validate the content format.
- Content Parameter Name mismatch: If integrating with third-party webhooks, ensure the custom content parameter name matches what the webhook sends.
- API rate limits: Frequent calls may hit Basecamp API rate limits; handle retries or backoff accordingly.
Common error messages usually relate to authorization failures, resource not found, or validation errors on the content.
Links and References
- Basecamp API Documentation
- Basecamp Chatbot API Reference
- n8n documentation on HTTP Request Node for understanding API interactions