Short answer: Drop the "ClickUp → List Lists" 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 |
|---|---|---|---|
Folder ID folder_id | string | Required | Folder ID. Example: 123456 |
Include Archived archived | options | Optional | Include Archived. Options: No, Yes |
{"folder_id": "e.g. 123456","archived": "{{trigger.archived}}"}
{"lists": [{"id": "list123","name": "Sprint 1","task_count": 15}]}
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.