Actions14
Overview
This node integrates with the Zoho Inventory API to manage inventory items, assemblies, and composite items. Specifically for the Item - Delete operation, it deletes an existing item from the Zoho Inventory system by its unique Item ID.
This node is useful in scenarios where you want to automate inventory management workflows, such as removing discontinued or obsolete items from your inventory database automatically. For example, after a product is no longer sold, you can use this node to delete it from Zoho Inventory to keep your records clean.
Properties
| Name | Meaning |
|---|---|
| Item ID | The unique identifier of the item to delete. This is required to specify which item should be removed from Zoho Inventory. |
Output
The output JSON object after a successful deletion contains:
success: A boolean indicating if the deletion was successful (true).message: A confirmation string, e.g.,"Item deleted successfully".
Example output:
{
"success": true,
"message": "Item deleted successfully"
}
No binary data is produced by this operation.
Dependencies
- Requires an OAuth2 API authentication credential configured for Zoho Inventory.
- The credential must include a valid Organization ID configured in its settings.
- The node uses Zoho Inventory's REST API endpoints to perform operations.
- Network connectivity to Zoho Inventory API endpoints is necessary.
Troubleshooting
- Missing Credentials: If the OAuth2 credentials are not set up or invalid, the node will throw an error indicating that Zoho Inventory credentials were not found. Ensure you have configured the OAuth2 credentials properly.
- Missing Organization ID: The Organization ID is mandatory. If missing or empty, the node will throw an error instructing you to configure it in the credential settings.
- Invalid Item ID: If the provided Item ID does not exist or is incorrect, the API may return an error. Verify the Item ID before attempting deletion.
- API Errors: Any other API errors returned by Zoho Inventory (e.g., permission issues, rate limits) will be surfaced as errors. Check the error message for details.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning the error message in the output JSON.