Short answer: Drop the "Zoho CRM → List Records" 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 |
|---|---|---|---|
Module module | options | Required | Module. Options: Leads, Contacts, Deals, Accounts |
Fields fields | string | Optional | Comma-separated field API names to return |
Sort By sort_by | options | Optional | Sort By. Options: Created Time, Modified Time, ID |
Sort Order sort_order | options | Optional | Sort Order. Options: Descending, Ascending |
Per Page per_page | string | Optional | Max 200 |
Page page | string | Optional | Page. e.g. "1" |
{"module": "{{trigger.module}}","fields": "e.g. Last_Name,Email,Company","sort_by": "{{trigger.sort_by}}","sort_order": "{{trigger.sort_order}}","per_page": "200"}
{"data": [{"id": "554023000001627036","Email": "john@example.com","Last_Name": "Doe"}],"info": {"page": 1,"count": 1,"per_page": 200,"more_records": false}}
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.