Pipeline cards
Cards represent individual items moving through Pipeline stages — deals, tickets, leads, or anything else.
A card is an individual item on a Pipeline board. Cards sit inside columns and move between them as progress is made. You can create cards manually from the board or automatically from a Workflow using the CREATE_CARD node.
Card fields
| Field | Type | Required | Notes |
|---|---|---|---|
| Name | String | Yes | The title shown on the card in the board view. |
| Description | String | No | Additional detail, notes, or context for the card. |
| Due date | Date/time | No | ISO 8601 timestamp for when the item is due (e.g. 2026-08-01T09:00:00Z). |
| Assigned to | User ID | No | The ID of the user responsible for this card. |
| Data | JSON object | No | An arbitrary structured payload stored with the card. Use this to attach any extra fields your process needs — deal value, contact info, external IDs, and so on. Defaults to {}. |
Moving cards between columns
Drag a card from one column to another directly on the board. You can also move cards automatically from a Workflow using the MOVE_CARD node — useful for advancing items when external events occur (a payment confirmed, a form submitted, a webhook received, etc.).
The data field
The data field is a flexible JSON payload for storing metadata that does not fit the other fields. It is fully schema-free: you can put any key-value structure in it.
Keep in mind: when the UPDATE_CARD node writes to data, it replaces the entire payload — it does not merge with the existing value. Include all keys you want to keep when updating.
Related
- Boards — the columns cards live in
- CREATE_CARD — create a card from a Workflow
- MOVE_CARD — move a card between columns from a Workflow
- UPDATE_CARD — patch card fields from a Workflow
- DELETE_CARD — remove a card from a Workflow
- Pipeline card nodes — full guide to automating card actions