Actions48
- Main Card Actions
- Card Actions
- Attachment Actions
- Workspace Actions
- Board Actions
- Tag Actions
- Sticker Actions
- Document Actions
Main Card → Get Card
AI-generatedOverview
This node operation retrieves detailed information about a specific card identified by its Card ID from the Main Card resource. It is useful in scenarios where you need to fetch and work with card data, such as project management, task tracking, or workflow automation. For example, you can use it to get the status, description, attachments, or custom fields of a card to display in a dashboard or trigger further actions based on the card's properties.
Use Case Examples
- Fetch a card's details by its ID to display in a project management dashboard.
- Retrieve specific fields like title, description, and due date of a card to send notifications or update other systems.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to retrieve. This is a required numeric input to specify which card's data to fetch. |
| Output | Determines the format of the output data. Options include Simplified (basic fields), Raw (full raw data), or Selected Fields (custom selection of fields). |
| Select Output Fields | Allows selection of specific fields to include in the output when 'Selected Fields' output option is chosen. Users can pick from a comprehensive list of card attributes such as annotations, attachments, deadlines, custom fields, owner ID, priority, status, and more. |
Output
JSON
card_id- Unique identifier of the card.title- Title or name of the card.description- Description text of the card.deadline- Deadline set for the card.owner_user_id- User ID of the card owner.priority- Priority level of the card.status- Current status of the card.attachments- Files or links attached to the card.custom_fields- Custom fields defined on the card.
Troubleshooting
- Ensure the Card ID provided is valid and exists; otherwise, the node may return an error or no data.
- If using 'Selected Fields' output, verify that the field names are correctly spelled and supported to avoid empty or incomplete results.
- Check API authentication credentials if the node fails to retrieve data due to permission issues.