Actions17
Overview
This node interacts with the Zoho Books API to manage customer payments, specifically allowing retrieval of customer payment details by email. It is useful in scenarios where you need to fetch payment information associated with a customer's email address, such as verifying payment status or reconciling accounts.
For example, if you have a customer's email and want to retrieve all their payment records from Zoho Books, this node operation will query the API and return the relevant payment data.
Properties
| Name | Meaning |
|---|---|
| Email (for Payment Get) | The email address of the customer payment to retrieve. This is used to filter and fetch payment records associated with the specified email. |
Output
The output is an array of JSON objects representing customer payment records retrieved from Zoho Books. Each object contains detailed fields about a customer payment, such as payment ID, customer ID, amount, date, payment mode, description, and applied invoices.
If the operation encounters an error, the output will contain an error field describing the issue.
No binary data is output by this node.
Dependencies
- Requires an OAuth2 API credential configured for Zoho Books with access to the organization.
- The credential must include the Zoho Books Organization ID.
- The node makes HTTP requests to the Zoho Books API endpoint specific to the organization's domain.
Troubleshooting
- Missing Organization ID: If the organization ID is not set in credentials, the node will throw an error indicating it is required.
- Email Not Provided: For "Get by Email" operation, if the email property is empty, the node throws an error stating that the email is required.
- API Errors: Errors returned by Zoho Books API are parsed and presented with code and message when available. Common issues include invalid email format, no matching records, or authentication failures.
- JSON Parsing Errors: If additional parameters are provided as JSON strings and are malformed, the node will throw an error indicating invalid JSON input.
To resolve errors:
- Ensure valid and complete credentials including organization ID.
- Provide a valid email address for the get-by-email operation.
- Check network connectivity and API permissions.
- Validate any JSON inputs before running the node.