Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
Overview
This node interacts with the "Card Tables" resource of a project management or collaboration platform (likely Basecamp, based on context). Specifically, it retrieves detailed information about a single card within a specified bucket. This is useful when you want to fetch and use data from a particular card in an automated workflow, such as displaying card details, updating other systems with card info, or triggering actions based on card content.
Practical examples:
- Automatically retrieving a task card's details to send a summary email.
- Fetching a card's metadata to update a dashboard or reporting tool.
- Using card information to trigger conditional logic in a workflow.
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 within the specified bucket. |
Output
The node outputs JSON data representing the full details of the requested card. This typically includes all properties of the card such as title, description, status, assigned users, due dates, comments, and any custom fields defined on the card.
If the card contains attachments or files, the node may also output binary data representing those files, allowing further processing or downloading within the workflow.
Dependencies
- Requires an API authentication token or OAuth2 credential configured for the target service (e.g., Basecamp).
- The node depends on the external service's API being accessible and the provided bucket and card IDs being valid.
- Network connectivity to the service's API endpoint is necessary.
Troubleshooting
- Invalid Bucket Id or Card Id: If either ID does not exist or is incorrect, the node will likely return an error indicating the resource was not found. Verify the IDs are correct.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key or OAuth2 token is properly set up.
- Network Issues: Timeouts or connection errors can occur if the service is unreachable. Check network connectivity and service status.
- Permission Denied: If the authenticated user lacks access rights to the bucket or card, the API will reject the request. Confirm permissions.
Links and References
- Basecamp API Documentation (for understanding card and bucket concepts)
- n8n documentation on Using API Credentials
- General info on Project Management Cards