1. Create : Execute the rule whenever a new record is created in the selected module
2. Create or Edit : Execute the rule whenever a new rule is created, or an existing rule is updated. If you want to repeat the workflow every time the record is modified, check the Repeat this workflow whenever a Deal is edited option.
3. Edit : Execute the rule when existing records are modified. You can configure the workflow to trigger when any field in the record is changed or when specific fields are updated. If you want to repeat the workflow every time the record is modified, check the Repeat this workflow whenever a Deal is edited option.
   
1. Any field gets modified : Select this option if you want to trigger the workflow whenever an existing record is modified, regardless of which field value is updated. Click Next.
   
   
2. Specific field(s) gets modified : Execute the rule when the values of the specified fields are modified in a record. You can add up to five fields for this condition. Choose the field and the modification condition for each. You can also choose whether to trigger the workflow if all or any of the given conditions are satisfied.  Click Next.
   
   
3. Any field in a specific section gets modified : For Leads, Contacts, Accounts, Deals, and custom modules, you can choose to trigger the workflow when any field in the specified sections gets modified. You can choose any system or custom sections from the system or custom layouts.
   
   NOTE : If a section is linked to a workflow rule, you need to delete the workflow rule before you can remove the section from the layout. Also, if the section includes fields such as Multiselect Lookup or File Upload, any changes made to these fields will not trigger the workflow rule.
4. Delete : Executes the rule when certain records are deleted. Only Email Notifications, Webhook and Functions can be associated with such a rule. 
   

2b. Date/Time field

There may be situations where you might want to schedule an email notification to customers a few days after a service has been completed, or send reminders for upcoming maintenance or warranty expirations. This trigger is based on the value of a date field, allowing you to automate actions without requiring records to be created or edited.

For instance, you can set up an activity to recur annually on the anniversary of a customer’s purchase, or schedule follow-up tasks a month after a project’s completion. When using this option, note that up to 5,000 records can be processed every 10 minutes. If the number exceeds 5,000 within that time, the remaining records will be processed in the subsequent 10-minute interval.

1. Select the Date/Time field from the available options, based on which you want to trigger the workflow.
2. Define the execution date.
3. Select the execution time.
4. Select the recurrence interval. You can choose to recur this Date/Time field based workflow once, every month, or every year.
   

2c. Record Notes

You can configure to trigger actions when notes are added, modified, or deleted.

1. All conditions must be met: The workflow is triggered when the lead’s purchase date is within the last 90 days and their annual revenue is greater than $500,000 and their status is Pre-Qualified. This ensures that the workflow targets only those leads who have recently made a purchase, are high-value, and are already pre-qualified.
2. Any condition can be met: The workflow is triggered if the lead’s purchase date is within the last 90 days or their annual revenue exceeds $500,000 or their status is Pre-Qualified. This approach allows the workflow to be executed for leads that meet at least one of the criteria.
   

Criteria Pattern:

You can create advanced filters using logical operators like AND and OR to fine-tune your criteria.

Key Points:

1. Maximum Criteria: You can define up to 25 criteria for a list view.
2. Mandatory Criteria: If you are applying a conversion action (an instant action) to the rule, defining criteria is required.
3. Lookup Fields: You can include up to 5 lookup fields in your criteria.
   

To Edit Criteria Patterns:

1. Navigate to Automation > Workflow Rules.
2. In the Workflow Rules page, select the rule you wish to edit.
3. Click on Edit Rule.
4. In the Edit Rule page, review your current criteria and click on the Change Pattern link.
5. In the Pattern Editor box, adjust your filters as needed. Use round brackets ( ) to group conditions, along with AND/OR operators to define the logical relationship between criteria. Use criteria row numbers to specify which criteria to include in the pattern. 
6. Click Save.
   

Step 4 - Define and add instant and scheduled actions

In the previous steps, you have:

1. Selected the Module: Selected the module to which the workflow rule will be applied.
2. Set the Trigger Conditions: Defined when the rule should be executed, such as based on record creation, updates, or other specified triggers.
3. Defined Record Criteria: Specified which records the rule should apply to based on specific conditions.
   

In this step, you can set up the actions that will occur when the workflow rule is triggered. You can choose between instant actions and scheduled actions to automate your processes effectively. These actions, once created, can be associated with many rules. You can either associate existing actions, or create one and associate with the workflow.

Instant Actions: These actions are executed immediately when the workflow rule is triggered. 

To add an instant action, click on Instant Actions, select the action you want to add, add the required details, and click on Save and Associate. For more information on adding each available instant action, please refer to the next section.

Scheduled Actions: These actions are set to occur at a specified time after the rule is triggered. 

To add a Scheduled action, 

1. Click on Scheduled Actions
2. Select the time at which you want the action to be performed. 
3. From the list, select the action you want to add. 
4. Add the required details
5. Click on Save and Associate. 
   

For more information on adding each available Scheduled action, please refer to the next section.

NOTE:

1. For a workflow rule, only those actions specific to the module will be listed. For instance, if the rule is for Leads, only actions created for Leads will be available for association.
2. If records are deleted via Workflow, their information cannot be retrieved using the get API as the records have already been deleted.
3. Edit or delete triggers do not function when records are auto-merged; these triggers will work if records are manually merged.
4. Only one set of instant actions can be created, which may include email notifications, tasks, meetings, calls, etc.
5. A maximum of 5 email notifications, 5 tasks, 5 field updates, 1 custom function, 1 webhook, and 1 create record action can be associated with the instant action.
6. The actions will execute in the following order: Field Update > Tags > Email Notification > Task > Webhook, Custom Function, and Create Record (executed in parallel).
7. Workflow rules execute an action the minute they are triggered. When a large volume of records that meet the trigger condition enters the system, the workflow may require some time to process the actions sequentially.
   

Add and associate actions to Rules

4.1 Field Update

The Field Update feature allows you to automatically modify specific field values in records whenever the associated workflow rule is activated. This can be configured as either an instant action or a scheduled action.

To add a Field Update action:

1. Click on Instant Actions/Scheduled Actions
2. Select Field Updates.
3. If you have pre-defined Field Update actions for the selected module, they will be listed. Select the one you wish to associate and click on Associate.
4. If you have no Field Update actions defined, create a new one by specifying the following details, and click on Save and Associate.
1. Name: Enter a name for the Field Update action.
2. Field: Select the field you want to update.
3. New Value: Specify the new value for the selected field.
5. Click on Save to save the workflow rule.
   

Please note that once actions are added, they will be available to be associated with other workflow rules as well.

4.2 Tags

You can add or remove tags from a record when a workflow rule is executed. This can be configured as either an instant action or a scheduled action.You can either use existing tags or create new ones during configuration.  

To add tags:

1. Click on Instant Actions or Scheduled Actions.
2. Select Tags > Add Tags.
3. Select from the list of available tags, or add new tags.
4. Specify whether to overwrite any existing tags in the selected records with the new tags.
5. Click Save.
   

To remove tags:

1. Click on Instant Actions or Scheduled Actions.
2. Select Tags > Remove Tags.
3. Choose the tags you want to remove from the record.
4. Click Save.
   

4.3 Email Notification

You can configure email notifications as instant or scheduled actions in a workflow rule. These notifications send alerts, updates, or information to leads, contacts, or internal users. By linking an email notification to a workflow, the system automatically sends the selected email to the designated recipients once the specified conditions are met.

To configure an email notification:

1. Click on Instant Actions or Scheduled Actions.
2. Select Email Notification.
3. If you want to use one of the pre-defined Email Notification actions, select one from the list, and click on Associate.
4.  If you want to create a new Email Notification action and associate with the workflow, click + Create Email Notification.
5. In the New Email Notification page:
1. Provide a name for the alert.
2. Choose the email recipients and click Save. The associated people will be displayed. If you select Roles/Groups/Territories/Subordinates, the email will be sent to users in the selected category.
3. Link an existing email template from the module's template folder, or create a new one if needed.
4. Specify email addresses in the From and Reply To fields. You can choose from the following options:
1. Your account email address
2. Organization email address
3. Record owner's email address
4. Current user's email address
5. Another user's email address
6. Click Save and Associate.
7. Click Save to save the workflow.
   

4.4 Activities : Add Tasks, Meetings, or Schedule Calls

Once you have set up the trigger and conditions for the workflow rule, you can add different activities as actions. Meetings and calls can be added as Instant actions, while tasks can be added either as instant actions or scheduled for later. This allows you to choose whether to handle tasks, meetings, or calls right away or plan them for a specific time, depending on your workflow needs.

Add a Task

A task assigns an activity to a user. When you link a task to the workflow rule, the system assigns it to the specified user once the rule is triggered for records that meet the criteria. You can add a task in both instant actions and schedules actions.

To create a workflow task:

1. Depending on whether you want an instant or scheduled action, click on Instant Actions > Activities > Add Task or Scheduled Actions > Task.
2. If you want to associate an already defined task, select the task and click on Associate. 
3. If you want to create a new task and associate it with the workflow, Click + New Task.
4. In the New Task window, follow these steps:
1. Enter a Subject for the task. Insert merge fields (#) to create dynamic task subjects.
2. Specify the Due Date for completing the task.
3. Choose the Status of the task from the drop-down list.
4. Set the task Priority from the drop-down list.
5. Assign the task to a user by selecting from the Assigned To lookup list.
6. Check the Notify Assignee box to send an email notification to the task owner.
7. Check the Remind Assignee box to send a reminder to the task owner.
8. Enter the task Description.
9. Click Save and Associate.
5. Click Save to save the workflow.
   

Add a Meeting

1. Navigate to Instant Actions and choose Activities > Add Meeting.
2. On the Add Meeting page:
1. Enter a title for the meeting.
2. Set the meeting time and duration by selecting the desired start time and interval in the From field.
3. Choose the duration and specify whether it is in minutes or hours.
4. If the meeting will last all day, check the All day option.
5. In the Host field, assign a user to lead the meeting.
6. If there's a chance the host might be unavailable, you can check the If the host is unavailable box to either create a task or assign the meeting to the record owner.
3. If additional information needs to be included in the meeting invite:
1. Click the Add more fields button.
2. Select any additional fields you want to include, such as participants, location, contact names, participant reminders, and meeting agenda.
4. Click Save.
   

Schedule a Call

1. Navigate to Instant Actions and choose Activities > Schedule a Call.
2. On the Schedule a Call page, specify the following:
   
1. Call Start Time and interval for scheduling.
   
2. Assign the Call Owner.
3. Select the reason for the call from the Call Purpose picklist.
4. Describe the Call Agenda.
5. For additional details, click on Add more fields to include information like the subject or to add a reminder.
3. Click Save.
   

4.5 Create a Record

You can set up instant or scheduled actions to create records based on specific conditions. For instance:

1. Automatically generate a purchase order when the vendor status changes to approved.
2. Create a follow-up task three days after a customer service request is logged.
   

You can create records in both standard and custom modules. Supported standard modules include Orders, Vendors, Accounts, Invoices, and Support Tickets. The action can be triggered by a record update or based on a specified Date/Time field. 

When configuring the rule:

1. Select the module where the new record should be created.
2. Select the layout in which the new record should be created.
   
3. Choose the record owner, either the logged-in user or another user in the system.  You can also assign the record to a user referenced by a lookup field in the layout. For example, if the Vendors module includes a user lookup for Accounts or Support Teams, you can assign the record owner from these related modules. Custom user fields can also be used as long as they are single-user fields.
4. Provide values for fields such as order number, total amount, etc. These values will be pre-filled in the new record. By default, mandatory fields from the layout will appear here, but you can add more fields and input values as needed, either manually or using merge fields. For example, you can use merge fields to populate the email address automatically.
5. Click Save.
   

Only one Create Record action can be defined per condition. When additional fields are added to the Create Record action, those fields will be required to complete the action.

4.6 Webhook

Webhooks enable integration with external applications by sending real-time web notifications, along with relevant data, whenever specified events occur. You can either associate an existing webhook to the workflow rule, or create a new one and associate with the rule.

To associate a webhook action:

1. Navigate to Instant Actions or Scheduled Actions and choose Webhook.
2. If you want to associate an already existing webhook, select from the list, and click Associate.
3. If you want to add a new webhook and associate it with the workflow rule,
1. Click on + New Webhook
2. Specify a Name for the webhook.
3. Add a description.
4. Choose the method as POST, GET, PUT or DELETE.
5. Specify the notification URL.
6. If required, add Module Parameters and/or Custom Parameters.
7. Select the body type and specify the body.
8. Click on Save and Associate.
4. Save the workflow rule.
   

4.7 Function

You can trigger a function when a workflow rule is executed. Functions allow you to automate complex tasks, such as updating data in related modules or integrating with third-party applications. When a record meets the criteria set in the workflow, the function is automatically executed to update the relevant records. These functions are created using Deluge Script, Zoho's scripting language, enabling you to automate a wide range of business processes.

To add and associate a function:

1. Navigate to Instant Actions or Scheduled Actions and choose Function.
2. If you want to associate an existing function, choose the function and click on Associate.
3. If you want to add a new function and associate it with the workflow rule:
1. Specify the Function Name.
2. Specify a Display Name.
3. Give a description for your function and click Create.
4. In the function editor, add your function code, and click on Save.
4. Click Save to save the workflow rule.

1. You can create up to 5 scheduled actions for a single workflow rule. Each of these actions can include a maximum of five email notifications, five tasks, five field updates, five custom functions, and five webhooks.
2. For each workflow rule, you can associate a total of six custom functions and six webhooks—1 as an instant action and 5 as scheduled actions.
3. If the Email Opt-Out option is enabled, emails will not be sent to customers. If the daily email limit is reached, any remaining emails scheduled for that day will not be sent.
4. Scheduled actions may experience a brief delay of a few minutes before they are triggered, especially if the calculated execution time is in the past.
5. Actions scheduled for a record will appear under the Upcoming Actions section on the record's details page.
6. You cannot save scheduled actions until you assign values to all mandatory fields within a meeting or call layout.
   
7. When a function updates records in related modules, you can configure it to trigger additional workflows in those modules. This allows you to create chains of automated actions. For example, updating an Account when a Policy changes, which then automatically updates related Contacts.

Instances When Scheduled Actions Will Be Deleted or Not Rescheduled:

1. When the execution criteria for a rule are set to Edit or Create or Edit, and a record no longer meets the criteria after an edit, the previously scheduled actions will not be rescheduled.
2. If a record is deleted, all scheduled actions for that record will be removed as well. If the deleted record is later restored, the scheduled actions will not be rescheduled.

Instances When Scheduled Actions Will Not Be Executed:

1. If an event is cancelled, any scheduled actions linked to that event will not be executed.
2. When a lead is converted, any scheduled actions associated with that lead will not be executed.
   

Lock Workflows

You can lock a workflow rule when you want to make sure no more changes are made to the rule. Once a rule is locked, one has to unlock the rule to edit it again. A locked rule sends out the message to fellow administrators that it is not meant to be edited unless absolutely required. A workflow rule can be locked after it has been created.

Note: For workflow rules published from the developer console, the lock workflow feature does not directly affect the subscriber, as they cannot edit the workflow. However, for workflows created by the subscriber, the lock feature functions as intended.

To lock a workflow rule:

1. Log in to Zoho Developer Console and click Vertical Studio.
2. Select the application you would like to modify and click Edit.
3. Click Automate in the left pane and select Workflow.
4. Select the workflow rule you want to lock.
5. Click on the lock icon near the rule name in the workflow rule page.
6. Give a brief description of why you want to lock the rule.
7. Click on Lock.
   

To unlock a locked workflow rule, click on the lock icon near the rule name.

Packaged Workflows

Packaged Workflows are workflows that are created in the console by a developer and deployed to the subscriber orgs during signup or through upgrade. 

Subscribers receive packaged workflow rules during signup or during later version upgrades. The workflow rule behavior is determined by the packaging configuration, and subscribers cannot modify the rule definition. However, they can view the rule activity and the results of automated actions in their org.

Tip: To know more about packaging, please refer to our help guide : Components Packaging in Zoho Solutions Platform.

The table outlines the behaviour of packaged Workflows.

Property	Upgrade Type	Subscriber Modify Access
Rule Name	Upgradable	No
Rule Description	Upgradable	No
Trigger type	Upgradable	No
Workflow conditions	Upgradable	No
Actions	Upgradable	No
Email notification template or recipients	Upgradable	No
Call activity configuration	Upgradable	No
Workflow Status	Not Upgradable	Yes
Order of WorkFlows*	Not Upgradable	Yes

Note:

The 'locked status' of Workflows cannot be packaged. By default, all workflows are deployed in the subscriber org in an unlocked, read-only mode.

Troubleshooting workflow issues

Workflow does not trigger

1. Check the following before investigating the rule logic:
2. The rule exists in the latest published application version.
3. The module and record type match the rule's selected module.
4. The trigger type matches the actual record event or date condition.
5. The record meets the condition set and the rule is not restricted by a missing field or invalid value.
6. The application version was published after the latest workflow change.

Rule is locked or changes do not save

1. Confirm that the current application version is published correctly.
2. Save the workflow definition again after the latest app state is consistent.
3. Refresh the rule editor and validate whether the trigger, condition, or action config still matches the latest published version.

Workflow fires for the wrong records

1. Confirm that the criteria are grouped correctly with AND and OR logic.
2. Check whether the trigger is set to Any field is modified instead of a specific field change.
3. Verify that lookup, date, and required-field values are not producing unintended matches.
4. Validate the rule in a test subscriber org using sample records that are close to real production conditions.

Trigger cascades or repeated execution

1. Check whether the rule updates a field that triggers the same rule again.
2. Confirm that a create-record or update action is not starting another workflow in the same module.
3. Review the exact sequence of actions to see whether the rule creates a record that re-matches the rule criteria.
4. Test the rule with a low-volume sample record so the repeated trigger pattern is easier to isolate.
   

Workflow sends the wrong email or wrong call activity

1. The correct recipients and sender values are selected in the email action.
2. The email template is the correct one for the module and use case.
3. The call or task action is assigned to the correct owner or host.
4. The assignee or subject values are not empty and do not depend on fields that are not present in the target record.
   

Scheduled workflow action is missing or delayed

1. The rule is configured for the correct date or time field.
2. The record still meets the rule conditions when the scheduled evaluation occurs.
3. The scheduled time is not set in the past in a way that prevents execution.
4. The action is still valid after a record update, delete, or lead conversion.
   

Date or time logic does not match expected UTC conversion

1. Confirm the target date field is stored and interpreted in the expected timezone for the application and subscriber org.
2. Check whether the rule compares a manually converted UTC value with a record value that is already localized.
3. Validate any custom formula or variable used to calculate the target date before the rule runs.
4. Test the same rule in a sample record with a known date near the edge of the day or week boundary.
   

Custom action configuration does not persist

1. Confirm that the selected custom function, webhook URL, or action variable is still valid after the last edit.
2. Review whether a field name, API name, or variable reference was renamed without updating the workflow action.
3. Save the workflow and refresh the action configuration to confirm the values remain in place.
4. Validate the custom action in a test subscriber org before shipping the version to production users.
   

Workflow works in one org but not another

1. If a workflow works in one subscriber org and not another, review the following:
2. The subscriber org is on the correct application version.
3. Different profiles or role permissions affect who can trigger or receive the action.
4. The workflow is not gated by a pricing-plan or visibility dependency.
5. The rule was published after the latest change and the subscriber org completed the upgrade.
   

Deleting a packaged workflow rule is a destructive change.

Removing a workflow rule from a published application will remove it from the subscriber orgs as well. This will stop notifications, task creation, and follow-up actions in subscriber orgs after the next upgrade. Validate the replacement process in a test org before removing a rule that subscribers are already depending on.