Actions76
- Bill Actions
- Contact Actions
- Credit Note Actions
- Invoice Actions
- Item Actions
- Sales Order Actions
- Tax Actions
- Tax Group Actions
- Tax Exemption (US only) Actions
- Vendor Actions
- Vendor Credit Actions
Sales Order → Get Many
AI-generatedOverview
This node interacts with the Zoho Books API to retrieve multiple sales orders based on specified criteria. It is useful for scenarios where you need to fetch a list of sales orders, such as generating reports, syncing data with other systems, or performing batch operations on sales orders.
For example, you can use this node to:
- Retrieve all sales orders created after a certain date.
- Limit the number of sales orders returned for performance reasons.
- Fetch only sales orders updated after a specific date to keep your local database in sync.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching sales orders or limit the results to a specified maximum number. |
| Limit | The maximum number of sales orders to return if "Return All" is false. Range: 1 to 200. |
| Date After | Filter to include only sales orders with an Order Date after this date (format YYYY-MM-DD). |
| Updated After | Filter to include only sales orders updated after this date (ISO format). |
Output
The output consists of an array of JSON objects, each representing a sales order retrieved from Zoho Books. Each item includes detailed information about a sales order, such as its ID, order date, status, customer details, line items, totals, and other relevant fields as provided by the Zoho Books API.
There is no indication that this node outputs binary data; it focuses on structured JSON data representing sales orders.
Dependencies
- Requires an active connection to the Zoho Books API using OAuth2 authentication.
- The node depends on proper configuration of the Zoho Books API credentials within n8n.
- No additional external services are required beyond Zoho Books.
Troubleshooting
Common Issues:
- Incorrect or expired API credentials will cause authentication failures.
- Requesting too many records without enabling pagination or limiting results may lead to timeouts or rate limiting.
- Providing invalid date formats for filters may result in errors or empty responses.
Error Messages:
"Unsupported resource": This error occurs if the resource parameter is set incorrectly or the resource is not implemented.- API rate limit errors: If too many requests are made in a short period, the API may reject calls temporarily.
Resolutions:
- Verify and refresh API credentials if authentication fails.
- Use the "Return All" toggle carefully; if disabled, set a reasonable "Limit".
- Ensure date inputs follow the required format (YYYY-MM-DD).
- Handle errors gracefully by enabling "Continue On Fail" if partial data retrieval is acceptable.