Zoho CRM workflow rules have historically only been configurable at the module level, meaning any automation tied to subform line items had to be tracked and actioned manually. A recent update changes this: workflow rules can now be triggered directly by actions taken within individual subform rows, giving teams far more precise control over how automation responds to detailed record data.

For example, in a Deals module containing a Product Details subform (where sales reps record each product line item against a deal), a rule could now fire the moment a Discount (%) value on a single product row exceeds 50 percent. This could instantly alert the sales manager and change the Approval Status field on the parent Deal record to "Pending review", so significant discounts are flagged and escalated without anyone needing to check for them manually.

Changes to the Workflow Rules home page

• Rules can now be built on either a module or a subform as their basis.
• Alongside the existing module filter, the home page now also supports filtering rules by subform.

Trigger options

A rule can be set to trigger on subform row events, such as a row being added, modified, added or modified, or deleted. It can also trigger on date and time fields, including created time, modified time, or a custom date field, with a defined execution time and recurrence. Where a rule responds to a row being modified, you can choose whether it should apply when any field changes, or only when specific fields change, and set your own conditions around that.

Building conditions across parent and subform data

• Subform-level conditions: apply logic directly to subform fields, so a rule only runs for rows that meet specific criteria, such as customised orders matching a certain profile.
• Parent module-level conditions: combine subform filters with conditions on the main record, for example order status, customer type or priority, so automation only fires for the exact combination of parent and row-level data you want.

Actions available once a rule fires

Once a trigger and its conditions are satisfied, a range of instant actions can run at the subform level, including field updates, email notifications, SMS notifications, webhooks and custom functions. A field update action can touch the subform itself, the parent module, or a related lookup module.

Using the Deals example above, a single trigger on the Product Details subform (row modified, Discount (%) over 50 percent) could run several field updates at once:

• Subform field: set Approval Required to "Yes" on the specific product row that triggered the review.
• Main module field: update Discount Approval Status on the parent Deal record to "Pending Review", fast-tracking it for sign-off.
• Lookup module field: update Last High-Discount Flagged Date on the linked Products record to the day the rule executed.

Release plan