Actions80
- 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
- Todos Actions
Overview
This node interacts with the "Card Tables" resource of an API (likely Basecamp, based on context) to retrieve details about a specific card within a bucket. It is useful when you want to fetch detailed information about a particular card stored in a card table, for example, to display its content, status, or metadata in your workflow.
Practical examples include:
- Retrieving task or project card details to update a dashboard.
- Fetching card information to trigger conditional logic based on card properties.
- Integrating card data into reports or notifications.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique numeric identifier of the bucket that contains the card. |
| Card Id | The unique numeric identifier of the card to retrieve from the specified bucket. |
Output
The node outputs JSON data representing the card's details as returned by the API. This typically includes all relevant fields describing the card such as title, description, status, assigned users, due dates, and any custom fields defined in the card table.
If the API supports it, binary data output is not indicated for this operation.
Dependencies
- Requires an API key credential for authentication with the external service (e.g., Basecamp OAuth2 token).
- The node uses a base URL constructed dynamically using the authenticated user's account ID.
- The node depends on the external API endpoint for card tables to fetch card data.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Card Id will cause the API call to fail.
- Authentication errors if the API key or OAuth token is invalid or expired.
- Network connectivity problems can prevent successful API requests.
Error messages:
- "Not Found" or similar indicates the specified bucket or card does not exist or is inaccessible.
- "Unauthorized" suggests issues with credentials; re-authenticate or check permissions.
- "Bad Request" may indicate malformed input parameters; verify Bucket Id and Card Id are correct numbers.
Links and References
- Refer to the official API documentation of the card tables resource for detailed schema and field descriptions.
- OAuth2 authentication setup guides for connecting to the external service.
- n8n documentation on how to configure API credentials and use HTTP request nodes for troubleshooting.