Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node interacts with the "Card Tables" resource of a project management or collaboration platform (likely Basecamp, based on context) to retrieve cards located within a specific column of a bucket. It is useful for workflows that need to fetch and process task cards or items organized in columns, such as Kanban boards or card tables.
Typical use cases include:
- Automating reporting or exporting tasks/cards from a particular column.
- Triggering actions based on the cards present in a specific column.
- Integrating card data into other systems or dashboards.
For example, you might use this node to get all cards currently in the "In Progress" column of a project board to generate a status report.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket (a container or grouping of columns) to query. |
| Column Id | The numeric identifier of the column within the bucket from which to retrieve the cards. |
Output
The node outputs JSON data representing the list of cards found in the specified column of the given bucket. Each card object typically contains details such as card ID, title, description, status, and other metadata relevant to the card.
If the node supports binary data output (not indicated here), it would represent attachments or files associated with the cards, but this is not evident from the provided code snippet.
Dependencies
- Requires an API key credential for authenticating with the external service (e.g., Basecamp API).
- Needs the Basecamp API base URL configured dynamically using the user's credentials.
- Depends on the
@devlikeapro/n8n-openapi-nodepackage for building properties from the OpenAPI specification.
Troubleshooting
- Missing or invalid Bucket Id/Column Id: Ensure these numeric IDs are correctly set and correspond to existing buckets and columns in your project.
- Authentication errors: Verify that the API key or OAuth2 token is valid and has sufficient permissions to access card data.
- Empty results: If no cards are returned, confirm that the specified column actually contains cards.
- API rate limits or connectivity issues: Check network connectivity and API usage limits.