Basecamp icon

Basecamp

Interact with Basecamp API

Actions76

Overview

This node interacts with the Basecamp API to retrieve cards within a specific column of a project’s card table. It is useful for workflows that need to fetch and process task or item cards organized in columns, such as project management automation, reporting on task statuses, or syncing card data with other tools.

For example, you might use this node to:

  • Automatically gather all cards from a particular column (e.g., "In Progress") to generate status reports.
  • Trigger actions based on cards present in a column, like sending notifications or updating external systems.
  • Aggregate card data for analytics or dashboard displays.

Properties

Name Meaning
Project ID The numeric ID of the project (bucket) containing the card table. Used in the API endpoint path.
Column ID The numeric ID of the column within the card table from which to retrieve cards. Used in the API endpoint path.
Return All Results Boolean option to return all cards in the column by paginating through results, or limit to a default number.
Return Full Response Boolean option to return the full HTTP response including status code and headers instead of only the response body.

Output

The node outputs JSON data representing the cards retrieved from the specified column. Each card object typically contains details such as card ID, title, description, position, and other metadata relevant to the card within the Basecamp project.

If the "Return Full Response" property is enabled, the output includes the entire HTTP response object, which contains status code, headers, and body.

The node does not output binary data.

Dependencies

  • Requires an authenticated connection to the Basecamp API via OAuth2 credentials.
  • Needs the Basecamp account ID configured in the credentials to construct the API base URL.
  • The node relies on Basecamp's REST API endpoints for projects, columns, and cards.

Troubleshooting

  • Invalid Project or Column 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: Ensure the OAuth2 credentials are valid and have sufficient permissions to access the project and card data.
  • Pagination Issues: When "Return All Results" is enabled, pagination depends on the API's Link header. If the API changes its pagination scheme, the node may fail to retrieve all cards.
  • API Rate Limits: Excessive requests may trigger rate limiting; handle errors accordingly and consider adding delays or retries.

Links and References

Discussion