Actions17
Overview
This node integrates with the Zoho Books API to manage contacts, invoices, and customer payments. Specifically for the Contact Delete operation, it allows users to delete a contact from their Zoho Books organization by specifying the contact's unique ID.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or incorrect contact records.
- Integrating with other systems to synchronize contact deletions.
- Managing contacts programmatically as part of larger workflows involving customer data.
Example use case:
- A workflow that removes contacts who have unsubscribed or are no longer relevant, ensuring the Zoho Books contact list stays current.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to delete. This is required to specify which contact to remove. |
Output
The output JSON contains an array of objects representing the result of the delete operation. For a successful deletion, the output includes:
success: A boolean indicating if the deletion was successful (true).message: A string message confirming the deletion or providing additional info.
Example output JSON:
[
{
"success": true,
"message": "Resource deleted successfully."
}
]
No binary data is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured for Zoho Books with access to the target organization.
- The credential must include the Zoho Books Organization ID.
- The node makes HTTP requests to the Zoho Books API endpoint corresponding to the user's domain.
Troubleshooting
- Missing Contact ID Error: If the Contact ID is not provided for the delete operation, the node will throw an error stating that the Contact ID is required. Ensure you provide a valid Contact ID.
- API Errors: Errors returned by Zoho Books API (e.g., invalid ID, permission issues) will be surfaced with details including error codes and messages when available.
- Invalid Credentials: If the OAuth2 credentials are missing or invalid, the node will fail to authenticate. Verify your API key/token and organization ID in the credentials.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.