Basecamp

Interact with Basecamp API

Actions76

Campfire Actions
- Create a Campfire Line
- Delete a Campfire Line
- Get a Campfire
- Get a Campfire Line
- Get Campfire Lines
- Get Campfires
Card Table Actions
- Create a Card
- Create a Column
- Get a Card
- Get a Card Table
- Get a Column
- Get Cards in a Column
- Move a Card
- Move a Column
- Update a Card
- Update a Column
Chatbot Actions
- Create a Chatbot
- Create a Chatbot Line
- Delete a Chatbot
- Get a Chatbot
- Get All Chatbots
- Update a Chatbot
Client Approval Actions
- Get a Client Approval
- Get Client Approvals
Client Correspondence Actions
- Get a Client Correspondence
- Get Client Correspondences
Client Reply Actions
- Get Client Replies
- Get a Client Reply
Client Visibility Actions
- Toggle Client Visibility
Comment Actions
- Get Comments
- Create a Comment
- Get a Comment
- Update a Comment
Document Actions
- Get Documents
- Create a Document
- Get a Document
- Update a Document
Event Actions
- Get Events
Forward Actions
- Get Forwards
- Get a Forward
Inbox Actions
- Get Inbox
Inbox Reply Actions
- Get Inbox Replies
- Get an Inbox Reply
Lineup Marker Actions
- Create a Marker
- Update a Marker
- Delete a Marker
Message Actions
- Get Messages
- Create a Message
- Get a Message
- Update a Message
Message Board Actions
- Get Message Board
Message Type Actions
- Create a Message Type
- Destroy a Message Type
- Get a Message Type
- Get Message Types
- Update a Message Type
Person Actions
- Get a Person
- Get My Profile
- Get People
- Get People on a Project
- Manage People on a Project
Project Actions
- Create a Project
- Get a Project
- Get Projects
- Trash a Project
- Update a Project
Question Actions
- Get Questions
- Create a Question
- Get a Question
- Update a Question
Question Answer Actions
- Get Question Answers
- Get a Question Answer
Questionnaire Actions
- Get Questionnaire
Recording Actions
- Get Recordings
- Trash a Recording
- Archive a Recording

Overview

This node integrates with the Basecamp API to create a new line (message) in a Campfire chat within a specified project. It is useful for automating communication workflows by programmatically posting messages to team chats hosted on Basecamp. For example, you can use this node to send notifications, updates, or alerts directly into a Campfire chat room as part of an automated process.

Properties

Name	Meaning
Project ID	The numeric ID of the Basecamp project (bucket) where the Campfire chat exists.
chatId	The numeric ID of the specific Campfire chat to which the message line will be added.
Content	The HTML-formatted text content of the Campfire line (message) to post.
Return Full Response	Boolean flag indicating whether to return the full HTTP response (status, headers, body) or just the response body.

Output

The node outputs JSON data representing the response from the Basecamp API after creating the Campfire line. This typically includes details about the newly created message line such as its ID, content, creation timestamp, and author information.

If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, including status code and headers, allowing for more detailed handling or debugging.

The node does not output binary data.

Dependencies

Requires an active Basecamp account with appropriate permissions.
Needs an API authentication token configured in n8n credentials to authorize requests to the Basecamp API.
The base URL for API requests is constructed using the account ID from the credentials.

Troubleshooting

Invalid Project or Chat ID: If the provided project or chat IDs are incorrect or do not exist, the API will return an error. Verify that the IDs correspond to existing resources in your Basecamp account.
Authentication Errors: Ensure that the API authentication token is valid and has sufficient permissions to post messages.
Content Formatting Issues: The content field accepts HTML; malformed HTML might cause unexpected rendering or errors.
API Rate Limits: Frequent calls may hit Basecamp API rate limits; handle such errors by implementing retries or backoff strategies.
Return Full Response Misuse: Enabling "Return Full Response" changes the output format; downstream nodes expecting only the body may fail if not adjusted accordingly.