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 interacts with the Basecamp API to retrieve detailed information about a specific Campfire chat room within a project. It is useful for scenarios where you need to fetch the current state or details of a Campfire, such as its messages, participants, or metadata, directly into your workflow. For example, you might use this node to monitor discussions in a project’s Campfire and trigger actions based on new messages or changes.
Properties
Name | Meaning |
---|---|
Project ID | The numeric ID of the project (also called bucket) that contains the Campfire. |
Campfire ID | The numeric ID of the Campfire chat room to retrieve. |
Return Full Response | Boolean option to return the entire HTTP response including status code and headers, or just the body content. |
Output
The node outputs JSON data representing the Campfire resource retrieved from the Basecamp API. This typically includes details such as the Campfire's ID, name, description, creation date, and possibly its messages or participants depending on the API response structure.
If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing status code, headers, and body instead of only the body content.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid Project ID and Campfire ID parameters.
- The Basecamp account ID must be configured in the credentials to construct the correct API base URL.
Troubleshooting
- Invalid Project or Campfire ID: If the IDs provided do not exist or are incorrect, the API will likely return a 404 error. Verify the IDs before running the node.
- Authentication Errors: Ensure the OAuth2 credentials are correctly set up and have sufficient permissions to access the specified project and Campfire.
- API Rate Limits: Frequent requests may hit Basecamp API rate limits; handle errors accordingly and consider adding delays or retries.
- Return Full Response Confusion: When enabling "Return Full Response," the output format changes. Make sure downstream nodes can handle the full response object.