Short answer: Drop the "Zoho Projects → List Tasks" 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 |
|---|---|---|---|
Portal ID portal_id | string | Required | Portal ID. Example: 12345678 |
Project ID project_id | string | Required | Project ID. Example: 123456 |
Start Index index | string | Optional | Start Index. e.g. "0" |
Range range | string | Optional | Range. e.g. "100" |
{"portal_id": "e.g. 12345678","project_id": "e.g. 123456","index": "0","range": "100"}
{"tasks": [{"id": "789","name": "Design mockup","status": "Open","priority": "Medium"}]}
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.