A workflow notification error in Zoho CRM means an alert or message that should have been sent by a workflow did not deliver or contained wrong/empty fields. This usually shows as failed flow notifications, missing Slack fields, or no emails sent when a workflow fires.
What it means — concrete explanation tied to the Zoho API surface
When a CRM workflow action that sends notifications (email, Slack, custom notifications in Zoho Flow) fails, the automation either stops sending messages or sends messages with unsupported/empty variables. Zoho Flow sends failure emails by default after 3 and 10 consecutive failures and can switch a flow off after 20 failures; custom notification settings control who is alerted and when [2]. In CRM integrations like Slack, variable placeholders that don’t match available CRM field tokens appear as "Unsupported_Field" because the integration could not resolve the CRM field at runtime [4]. Inconsistent or malformed data (for example phone numbers not in E.164) causes actions that expect exact formats to fail or behave inconsistently [1]. Time-based automation changes may not trigger webhooks if the action origin or history shows the update came from a time-based process rather than a user action [7].
Common causes
- Mismatched field tokens or variable names in the notification template, causing "Unsupported_Field" output in Slack or emails [4].
- Data format or missing required values (phone numbers, email, or ID fields) that the workflow action expects exactly [1].
- Flow execution limits and repeated failures hitting the Flow failure threshold, which can auto-disable a flow if it fails many times [2].
- Time-based or system-sourced updates that do not emit the same webhook/event payload as user actions, so downstream webhooks or integrations don’t trigger [7].
How to fix it
- Reproduce the failure in a test record. Note the exact workflow, action type (email, webhook, Slack), and the time of failure. Check the workflow history for the record.
- Verify template variables: open the notification template and reinsert field tokens using the template picker. If a field list does not appear when typing "#", re-open the integration and re-authorize it, then recreate the token insert to avoid "Unsupported_Field" placeholders [4].
- Validate data on failing records. Run a filter for records that failed and check required fields and formats (E.164 for phone numbers, correct email format). Fix a sample record and re-run the workflow to confirm success [1].
- Inspect Flow settings and failure counts. If a Zoho Flow is failing repeatedly, check the Flow failure emails and custom notification settings, then fix the root error and reset or re-enable the flow once fixed [2].
- For webhook/time-based issues, check the action origin in record history. If time-based automations do not trigger webhooks, convert the action to a workflow rule that emits the correct event or add a custom function to explicitly call the webhook [7].
- Re-run and monitor: once changes are applied, re-trigger the workflow for a sample set and watch logs or flow run history to verify success.
When to escalate
Open a Zoho support ticket when you can reproduce the failure after the above steps, have logs or flow run IDs, and the issue involves platform-level behavior (flows auto-disabled without clear error, API responses indicating internal errors, or missing platform tokens). Include screenshots, record IDs, and timestamps to speed diagnosis.