Zoho CRM Custom icon

Zoho CRM Custom

Consume Zoho CRM API

Overview

The Zoho CRM Custom node for n8n allows you to interact with the Zoho CRM API. Specifically, when using the Purchase Order resource and the Get Many (getAll) operation, this node retrieves multiple purchase order records from your Zoho CRM account. You can filter, sort, and limit the results according to your needs.

Common scenarios:

  • Fetching all or a subset of purchase orders for reporting or integration with other systems.
  • Filtering purchase orders by approval status, conversion status, territory, or custom fields.
  • Automating workflows that require up-to-date lists of purchase orders.

Practical examples:

  • Retrieve all approved purchase orders for a specific territory and send them to an accounting system.
  • Get the latest 10 purchase orders sorted by creation date for dashboard display.

Properties

Name Type Meaning
Return All Boolean Whether to return all results or only up to a given limit. If false, 'Limit' is applied.
Limit Number Maximum number of results to return (only shown if 'Return All' is false).
Options Collection Additional filters and settings for the query (see below for details).

Options sub-properties:

Name Type Meaning
Approved Boolean Whether to retrieve only approved records. Defaults to true.
Converted Boolean Whether to retrieve only converted records. Defaults to false.
Fields MultiOptions Return only these fields in each record.
Include Child Boolean Whether to retrieve only records from child territories.
Sort By Options Field to sort records by.
Sort Order Options Ascending or descending order sort order.
Territory ID String Retrieve only records from this territory.

Output

  • The output is an array of JSON objects, each representing a purchase order record from Zoho CRM.
  • The structure of each object depends on the selected fields and options, but typically includes standard purchase order properties such as IDs, subject, vendor, status, dates, and any custom fields present in your Zoho CRM instance.
  • If the "Fields" option is used, only those fields will be included in each output object.

Example output:

[
  {
    "id": "1234567890",
    "Subject": "Office Supplies",
    "Vendor_Name": { "id": "987654321", "name": "Acme Corp" },
    "Status": "Approved",
    "Created_Time": "2024-05-01T12:34:56+00:00",
    ...
  }
]
  • No binary data is returned by this operation.

Dependencies

  • External Service: Requires access to a Zoho CRM account.
  • Authentication: Needs valid Zoho OAuth2 credentials configured in n8n (zohoOAuth2Api).
  • n8n Configuration: Ensure the Zoho CRM API credentials are set up in n8n's credential store.

Troubleshooting

Common issues:

  • Invalid Credentials: If authentication fails, ensure your Zoho OAuth2 credentials are correct and have sufficient permissions.
  • API Limits: Zoho CRM may enforce rate limits; excessive requests could result in errors.
  • Field Selection Errors: Specifying non-existent or misspelled field names in the "Fields" option may cause errors or empty results.
  • Territory/Filter Mismatch: Using invalid territory IDs or filter combinations may yield no results.

Error messages and resolutions:

  • "Invalid value for parameter": Check that all input parameters (especially IDs and field names) are correct.
  • "Request failed with status code 401": Authentication issue—refresh or reconfigure your Zoho OAuth2 credentials.
  • "No records found": Adjust your filters or check that there are matching purchase orders in Zoho CRM.

Links and References

Discussion