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
The node interacts with the Basecamp API to retrieve detailed information about a specific Card Table within a project (referred to as a "bucket" in Basecamp). This operation is useful when you want to fetch the current state or metadata of a particular Card Table, such as its name, description, cards it contains, and other related details.
Common scenarios include:
- Synchronizing card table data from Basecamp into another system.
- Displaying card table details in dashboards or reports.
- Automating workflows that depend on the structure or contents of a card table.
For example, a project manager might use this node to pull the latest card table data to review task statuses or to trigger notifications based on card updates.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) containing the card table. Used in the API endpoint path. |
| Card Table ID | The numeric ID of the card table to retrieve. Used in the API endpoint 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 requested Card Table's details. This typically includes properties such as the card table's ID, name, description, creation date, update date, and the list of cards it contains along with their attributes.
If the "Return Full Response" property is enabled, the output will include the full HTTP response object, which contains:
- Status code
- Headers
- Body (the card table data)
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to access projects and card tables.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies are required beyond the Basecamp API access.
Troubleshooting
- Invalid Project ID or Card Table ID: If the IDs provided do not exist or the user lacks permission, the API will return an error. Verify that the IDs are correct and that the authenticated user has access rights.
- Authentication Errors: Ensure the OAuth2 credentials are valid and have not expired.
- Network Issues: Connectivity problems can cause request failures; check network settings and Basecamp service status.
- Unexpected Response Format: If the API changes or returns unexpected data, the node may fail to parse the response correctly.