Short answer: Drop the "Trello → Create Card" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
List ID idList | string | Required | Trello list ID — 24-char hex. Find via List Lists on a board. |
Card Name name | string | Required | Card Name. Example: Review PR #42 |
Description desc | string | Optional | Card description (supports Markdown) |
Position pos | options | Optional | Position. Options: Top, Bottom |
Due Date due | string | Optional | ISO 8601 date |
Member IDs idMembers | string | Optional | Comma-separated Trello member IDs to assign |
Label IDs idLabels | string | Optional | Comma-separated label IDs |
{"idList": "e.g. 5abbe4b7ddc1b351ef961414","name": "e.g. Review PR #42","desc": "{{trigger.desc}}","pos": "{{trigger.pos}}","due": "e.g. 2025-06-30T17:00:00.000Z"}
{"id": "card123","name": "Review PR #42","idList": "list123","shortUrl": "https://trello.com/c/abc123"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.