List Contacts: Zoho Books action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Organization ID organization_id	string	Required	Organization ID. Example: 10234695
Search search_text	string	Optional	Search. Example: Bowman
Page page	string	Optional	Page. e.g. "1"

Sample request

{
  "organization_id": "e.g. 10234695",
  "search_text": "e.g. Bowman",
  "page": "1"
}

Returns

{
  "code": 0,
  "contacts": [
    {
      "email": "john@bowman.com",
      "contact_id": "460000000026049",
      "contact_name": "Bowman Furniture",
      "contact_type": "customer"
    }
  ],
  "page_context": {
    "page": 1,
    "per_page": 200,
    "has_more_page": false
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Contacts.

What does the List Contacts action do in Zoho Books?

Lists contacts (customers and vendors) from Zoho Books with their balances and status. Used for AR/AP reports or contact pickers.

What inputs does List Contacts require?

Required: Organization ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Zoho Books returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Contacts support batch operations?

Yes. Run List Contacts inside a Loop node to process arrays. Tiny Command handles Zoho Books's rate limits automatically so you don't have to throttle manually.

More actions