The Logic section contains elements to build the logic part of your workflow. It's like the control center of your automation, directing the flow of actions based on specific conditions.
The logic section has three main parts:
- Flow Control is like a traffic light for your workflow, ensuring that actions are executed in the right order and under the right conditions. It lets you create variables, branching paths, and also set delays that make your automation more flexible and adaptable.
- Notifications are like the alarm clocks for your workflow, , keeping everyone updated on important events and progress. You can use them to send alerts, error messages, or status updates to stakeholders, ensuring that everyone is on the same page.
- Custom Functions are like the building blocks of your workflow, letting you create reusable chunks of code that can be used throughout your automations. This saves time, reduces code duplication, and makes your workflows easier to maintain and understand.
Flow Control
Set Variable
Set variable allows you to create a variable and assign it a value. The value can be a constant, the result of a formula or data from triggers or actions.
- Use constant values
Assign a fixed value to a variable.
Example: cost=30
- Using Formulas
Perform calculations before assigning the value.
Example: total= ${trigger.total+10}
- Trigger or Action Output Variables
Use output variables from triggers or actions to create variables.
Example: userame=${trigger.first_name+trigger.last_name}
- Other Set Variables
Refer to values from other variables to create new variables.
Example: total=${cost+trigger.total}
To configure Set Variable :
- Click on the Logic tab on the left side of the builder.
- Drag and drop Set Variable from Flow Control.

- In the configuration window that opens, the variable name will be auto filled. You can edit the name if needed.
- Enter a value that will be stored in the variable. Example: ${trigger.total+10}
- Click Done. You will now be able to map this value in the actions that follow.

Note:
- All variable names must start with a letter.
- Variable names can contain alphanumeric characters and underscores.
- Other characters, such as spaces, are not accepted. Names must be unique to avoid naming clashes.
- If you use the assign values to a variable in multiple actions,then the result of the action executed last will be stored in the variable.
Decisions
Decisions act as control points within your workflow, evaluating conditions and directing the flow accordingly. You can define rules to check for specific criteria and specify actions to be executed when those conditions are met, enabling you to create more sophisticated and adaptable workflows that respond effectively to diverse scenarios.
For example, the workflow can take different actions based on the subject of an email. If the email has the subject "Order Received," it will extract invoice details and purchase numbers from the email content. It will then mark the corresponding order as received in the web application and send a success notification email. Similarly, when the subject is "Create Purchase Order," the workflow initiates a process to generate a new purchase order in the web application. In the case of the subject "Order Confirmed," it triggers a sequence to update the order status to "confirmed" in the web application.
Conditions
Each test case that you define is called a condition. You can create multiple test conditions, each of which can be a combination of one or more rules linked using logical AND or OR operators.
Groups
A group is a collection of rules. You can add as many groups as required. The final value is evaluated from the output of each group, rather than from the output of a single rule.
Operator Precedence
Logical AND operators are given higher precedence than OR operators. For instance, consider the following condition where T is true and F is false:
T||F&(T&T)
In this case, the evaluation is performed as follows:
- (T&T) - Evaluates to true
- T||(F&T) - The result of F&T is false
- T||F - Evaluates to true
Therefore, the overall output of the condition is true.
To configure Decision:
- Click the Logic tab on the left side of the builder.
- Drag and drop Decision from Flow Control.

- In the configuration window, define your conditions. All output variables from previous tasks will be available in the dropdown. Choose a variable, select the operator, and specify the value for comparison.
- You can add multiple conditions and use Logical AND or OR to link them. Include different test conditions within a group or create additional groups as needed. Adding a group or test condition will display a dropdown with AND/OR options:
"AND" indicates the output is true only if both test conditions are true.
"OR" indicates the output is true if one or both test conditions are true. Click Add Group below your test condition to create a new group.
Add as many conditions as you need by clicking the
+ below your conditions in the flow builder. You can also add an action to execute when none of the conditions hold true at the bottom of the decision box. This is called the default action.

Here, an email notification is triggered when both the conditions are false.

Note:
The dropdown will list all output variables available from the action outputs. For fields that require manual extraction, such as from Read data from Excel action, you'll need to create a new variable and assign the desired value to it. This new variable can then be used in the condition.
Output variables received from a webhook trigger should also be assigned to new variables using the Set Variable action before they can be used in conditions
Delay
The Delay action provides a convenient way to pause the execution of a workflow for a specified period before resuming the flow. This feature is particularly useful in situations where you need to introduce a time gap between actions or wait for an external event to occur before proceeding.
For instance, consider a lead nurturing workflow that sends an initial welcome email to a new subscriber and then follows up with additional emails at intervals of two days or five weeks to provide valuable resources, schedule a webinar, or gather feedback on their product experience.
You can also use delays to pause workflow executions to introduce pauses between actions for data processing or system updates, align actions with business hours or customer schedules, and await external events such as API responses or user interactions.

Note: You can use natural language to input dates and time periods into the Delay for option. For example, Flow will accept entries like "3 days", "a month," or "four weeks." Your current time will be used as the starting time for the duration. If you create a three-day delay action at 2PM, it will be executed at 2PM three days from the date you created it.
To configure Delay:
- Click the Logic tab on the left side of the builder.
- Drag and drop Delay from Flow Control. There are two types of Delay: Delay For and Delay Until.

- Delay For will be auto-selected. You can choose to delay for any number of minutes, hours, days, or weeks.
- You can choose to Delay until a particular date you select from the calendar. Click on the month or year to view your options for changing them.
- Click Done.
Notification
Send Email
Send Email allows you to send an email to any email domain through workflows. The sender address won't be yours, but the Reply to will be set to your email address (any domain). For example, you can configure an email to be sent from your official email address (your company's custom domain) to all candidates who applied for an opening. Although the email will be sent from our auto-generated email address, the Reply to will be set to the sender email address you provide.
To configure Send Email:
- Click the Logic tab on the left side of the builder.
- Click Notifications.
Drag and drop Send Email to the builder. A configuration window will open where you need to fill in the following details
From | Sender email address (Reply to will be set to this email) |
| ToClick Done. | Recipient email address |
| Subject | Subject of the email |
Message | |
For more options, click Advanced options below the message field.
Cc | Carbon copy. Email addresses you want to forward a copy of this email to. |
| BCC | Blind carbon copy. Email addresses you want to forward a copy of the email to but do not want the other recipients to know. |
- Click Done.
How do I verify my email address?
The Send Email action allows you to send emails through workflows with the From address of your choice (for example, sales@yourdomain.com). As the emails are sent from Zoho RPA's mail servers, you are required to verify the validity of the From addresses you provided. Once you complete the verification, the emails will be sent with the verified email address as From and Reply to address.
To verify the email address, follow these steps:
- Click Add new email address adjacent to the From address field.

- Provide the email address that you want to use as the From address in the Email ID field and click Verify.
- A One Time Password (OTP) will be sent to the email address provided. Enter it in the Verification Code field and click Verify to complete the verification.

Note: If you do not complete verification,
noreply@zohorpa.com will be used as the default From address.
Custom Functions
Create your own function from scratch in Zoho RPA using Deluge script.
Learn more