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 interacts with the Basecamp API to retrieve detailed information about a specific card within a project’s card table. It is useful when you need to fetch data about a particular card identified by its unique ID and the project (bucket) it belongs to. Typical use cases include automating workflows that require accessing card details for project management, reporting, or integration with other tools.

For example, you might use this node to:

Retrieve the status or content of a task card in a project.
Fetch card metadata to update dashboards or send notifications.
Integrate card information into custom reports or analytics pipelines.

Properties

Name	Meaning
Project ID	The numeric ID of the project (also called bucket) where the card resides; used in the API path.
Card ID	The numeric ID of the card to retrieve; used in the API path.
Return Full Response	Boolean option to return the entire HTTP response including status code and headers instead of just the response body.

Output

The node outputs JSON data representing the card's details as returned by the Basecamp API. This typically includes all properties of the card such as title, description, status, assigned users, creation date, and any other metadata provided by the API.

If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing:

Status code
Headers
Body (the card data)

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 and card IDs.
Proper API credentials must be configured in n8n to authenticate requests.

Troubleshooting

Invalid Project or Card ID: If the provided IDs do not exist or are incorrect, the API will likely return a 404 error. Verify the IDs before running the node.
Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the OAuth2 credentials are correctly set up and authorized.
API Rate Limits: Excessive requests may trigger rate limiting by Basecamp. Implement retry logic or reduce request frequency if needed.
Return Full Response Confusion: Enabling "Return Full Response" changes the output structure. Make sure downstream nodes handle the full response format accordingly.