1. Overview 

A workflow is a sequence of automated steps that define how tasks, information, or processes progress through an application. They help to improve efficiency, maintain consistency, and reduce manual intervention in routine operations. Most workflows follow a trigger-action model, where a specific event initiates one or more predefined actions.

In Zoho Creator, workflows are rule-based automations that streamline business processes by executing specific actions when defined events occur, such as form submissions, field updates, or scheduled triggers. They help eliminate repetitive tasks, enhance operational efficiency, and ensure accurate data processing across your Creator application. When a workflow is triggered, it automatically carries out the configured actions, such as sending notifications, updating or creating records, managing approval processes, or integrating with external systems, enabling you to build responsive, intelligent, and scalable applications with ease.

3.1. Workflow types 

Zoho Creator offers various workflow types to address different automation needs within your application:

1. Form workflows -  Trigger actions automatically based on user interactions in form such as record events (such as create, edit, or delete), and form event (like form load, field input, or form submission).
   
2. Schedules - Run automated actions at fixed time or based on data stored in the date field in the form.
   
3. Approvals - Automate multi-level review processes by routing records to designated approvers and executing actions based on approval or rejection outcomes.
   
4. Payments - Enable online payment collection through forms and trigger actions based on successful or failed transactions using integrated payment gateways via Zoho Checkout.
   
5. Blueprints -  Enforce a structured process by defining each stage and its transitions, similar to modeling workflows using BPMN (Business Process Model and Notation), guiding users through predefined conditions, and actions for consistent process execution.
   
6. Batch workflows - Execute custom Deluge scripts on large volumes of records either after data import or at scheduled intervals, enabling bulk processing and automation.
   
7. Report workflows - Trigger actions from user activities on reports using custom action items.
   
8. Functions - Define reusable logic blocks using Deluge that can be invoked across workflows and applications to maintain consistency and reduce redundancy.
   

3.1.1. Form workflows 

These workflows execute predefined actions automatically when triggered by user interactions on a form, such as creating, editing, or deleting a record. Each form can have multiple workflows, which are executed sequentially based on their order of creation. You can associate a variety of actions with a form workflow, such as sending notifications, updating field values, modifying records, or integrating with third-party services to streamline operations and minimize manual effort. Learn more about form workflows and their actions.

1. When a user submits a feedback form, a workflow is triggered to send a thank-you email to the user and create a follow-up task for the support team.
   
2. When a new item is added to the inventory form, a workflow is triggered to update the stock level and notify the warehouse team.
   
3. When a customer submits an enquiry form, a workflow is triggered to push the data to Zoho CRM and create a lead record.
   

Key benefits

1. Automated execution: Automatically perform actions like sending emails or updating records when users interact with a form.
   
2. Dynamic client actions: Let you configure client functions in Creator without scripting, such as showing, hiding, enabling, or disabling form fields based on real-time user input for a personalized experience.
   
3. Data accuracy: Apply validations and field rules to ensure clean and consistent data entry.
   
4. Integrations: Connect with third-party services like Zoho CRM or QuickBooks without complex scripting.
   
   

3.1.2. Schedules 

These workflows allow you to execute predefined actions automatically at specific times, without requiring user interaction. They are triggered either at a fixed date and time or based on the data stored in a form's date field. You can automate tasks such as sending emails, updating records, or running custom scripts, enabling time-based process automation across your application. Schedules can also include conditions to execute actions only for selected records, enhancing control and efficiency. Learn more about schedule workflows and their actions.

1. The product delivery tracker application triggers a schedule to send an installation reminder SMS to the customer as soon as the product's delivery date is reached.
   
2. A maintenance application triggers a schedule to notify technicians about upcoming equipment service dates.
   
3. When a project deadline date approaches, a schedule is triggered to notify the assigned team members and update the project status.
   
4. When the warranty end date is reached for a product, a schedule automatically sets the product status to Out of Warranty in the inventory form.
   

Key benefits

1. Time-based automation: Run workflows on specific dates or intervals without user input.
   
2. Productivity: Handle repetitive tasks like reminders, status updates, and scheduled emails.
   
   

3.1.3. Approvals 

Approval workflows automate the review and decision-making for records or requests that require multiple levels of approval. This eliminates the manual effort of sorting and forwarding records to approvers. They involve the process of routing records submitted through a form to assigned approvers sequentially, based on predefined criteria. Multiple approval levels can be specified for each level and define actions to execute on approval or rejection. Learn more about the approval workflow and its actions.

1. When a vendor submits a quotation through the procurement management application, the approval workflow routes it first to the purchase manager for review, and then to the finance team for final approval based on the quoted amount.
   
2. In an expense management application, when an employee submits an expense report, the workflow evaluates the expense amount and routes it through different approval paths accordingly. Expenses up to $100 may be approved by the team lead, while expenses above $100 may be routed to a manager for further review after the lead’s approval.
   
3. Within a leave management application, leave requests are routed based on duration: requests for less than a day are not sent for approval, those exceeding a day require team lead approval, and continuous leave beyond five days is escalated to a manager for approval.

Key Benefits

1. Accelerate approvals: Automate complex multi-level approvals to reduce delays and improve process efficiency.
   
2. Customizable Approval Rules: Define approval criteria and multiple levels tailored to organizational policies and workflows.
   
3. Accountability: Assign specific approvers and track approval history for audit and compliance.
   
4. Automated actions: Trigger follow-up actions like notifications, record updates, or escalations on approval or rejection.
   
   

3.1.4. Payments 

In Zoho Creator, payment workflows enable secure and automated online payment collection through forms using Zoho Checkout, which integrates with multiple industry compliant payment gateways. You can configure when a payment should be collected based on specific form criteria, and define actions that are triggered upon payment success or failure, such as sending confirmation emails, updating customer records, or logging transaction details. Zoho Creator also supports linking multiple gateways via Zoho Checkout within a single account, allowing you to route transactions through different providers based on application logic, regional requirements, or business rules. This eliminates the need for external configurations and provides flexibility in managing payment processing. Learn more about payment workflows and its actions.

1. When a customer places an order through the order management application, a payment workflow is triggered to collect the total amount and send a confirmation email upon successful payment.
   
2. In the certification registration application, when a user registers for a workshop, the workflow redirects them to the payment gateway, processes the registration fee, and stores the transaction ID for future reference.
   
3. When a donor fills out a form in the donation management application, a payment workflow collects the amount, updates donation records, and adds the donor's contact to Zoho CRM.
   
4. Upon submitting a booking request in the event booking application, the payment workflow captures the payment, confirms the booking, and redirects the user to a thank you page.
   

Key benefits

1. Integrated Payments: Collect payments directly through forms using supported gateways like Stripe, RazorPay, PayPal, Authorize.Net, Forte, Paytm, and PayTabs
   
2. Automated Follow-ups: Trigger automated emails, form updates, or data logging based on payment success or failure.
   
3. User Experience: Redirect users to the payment gateway and back to your app without any manual steps.
   
4. Secure Transactions: Creator has encrypted, verified payment connection for secure payment handling and status tracking.
   
   

3.1.5. Blueprints 

Blueprint workflows allow you to implement and manage structured business processes by guiding users through well-defined, stage-based workflows. Each process is divided into stages (milestones) and transitions (actions required to move from one stage to another), ensuring that the process progresses in a controlled and consistent manner.
Transition rules can be configured with criteria, permissions, and ownership to ensure that only authorized users can perform actions at the right stage. During transitions, data can be collected from users, and after transitions, automated actions can be triggered based on the configured logic.

1. Common transitions: They are always available for execution regardless of the current blueprint stage. Unlike regular transitions, which are used to move a record from one stage to another, a common transition can be triggered at any point in the process. This allows users to perform essential actions, such as canceling a request or flagging an issue without interrupting the main workflow logic.
   
2. Parallel transitions: They are used when multiple transitions must be completed before a record can move to the next stage. Each parallel transition can be executed independently, but the process only progresses to consecutive stage once all required transitions are completed.
   

Blueprint helps eliminate process inefficiencies, enhances cross-team collaboration, and reduces manual errors by clearly defining how a record should progress through each phase. Learn more about blueprints and its actions.

1. In the leave management application, when an employee applies for leave, the record progresses through stages such as leave requested, manager review, and HR approval. At each stage, only authorized personnel, like the respective manager or HR can perform transitions such as accept or decline, based on their role.
   
2. In the vendor onboarding application, parallel transitions allow both the finance and legal teams to carry out their evaluations simultaneously. The record proceeds to the next stage only after both teams complete their respective checks.
   
3. In the order management application, a common transition enables the customer to cancel an order at any stage, whether it’s order placed, packed, or shipped, ensuring the cancellation option remains accessible throughout the process.
   

Key benefits

1. Defined workflow path: Guide users step-by-step through complex business processes with visual workflows and clearly marked milestones.
   
2. Role-based execution: Ensure that only the designated users or roles can act on a transition using criteria, user fields, or permission sets.
   
3. Parallel & common transitions: Provide flexibility by enabling parallel transitions, where multiple actions must be completed simultaneously before progressing to the next stage, and common transitions, which can be executed at any point in the process regardless of the current stage.
   
4. Process visibility: Track, monitor, and audit the progress of each record through the defined stages to verify and ensure accountability.
   
   

3.1.6. Batch workflows 

Batch workflows enable you to efficiently execute customized Deluge scripts on large volumes of data, either after successful import or at scheduled intervals. These workflows split bulk records into smaller batches ranging from 10 to 1000 records per batch and run actions for every record within each batch. You can also configure actions to run before and after batch execution, allowing you to initialize variables or handle notifications and cleanups. It lets you process large volumes of data in smaller chunks during off-peak hours, automating high-volume, repetitive tasks to minimize system load and maximize productivity. These workflows run asynchronously and can be scheduled or triggered automatically after importing records into your application. Learn more about batch workflows and its actions.

1. In the payroll management application, when monthly salary slips need to be sent to all employees, a batch workflow processes payroll data in manageable chunks and automatically emails the payslips.
   
2. The inventory management application uses batch workflows to periodically check stock levels of all products, trigger restocking alerts, or update inventory records, ensuring stock availability without the overhead of real-time processing.
   
3. In the order fulfillment application, all orders received during the day are collected and sent as a consolidated list to the warehouse team for packing and shipping. This batch approach improves operational efficiency and reduces system load during peak hours.
   

Key benefits

1. Efficient Processing: Handles large volumes of data by breaking it into smaller batches to avoid execution limits and timeouts.
   
2. Automated Scheduling: Run batch workflows at specific times or after data imports to automate routine tasks.
   
3. Error Isolation: Errors in one batch do not affect the processing of others, reverting only the failed batch.
   
4. Actions: Configure actions to run before, during, and after batch execution for initialization, processing, and cleanup.
   
5. Data synchronization: Keep data up-to-date by periodically syncing with external systems or cleaning outdated records.
   
   

3.1.7. Report workflows 

These workflows are executed directly from the report in your Zoho Creator application. They are triggered by action items, which serve as customizable additions to the default report actions such as edit, delete, duplicate, and view record. Action items appear as buttons or menu options in the quick view or detailed view of a record in a report, enabling users to interact with report records using logic based on the specific business needs. Adding an action item involves configuring a workflow that encapsulates the action to be executed when the button is clicked. Once configured, the custom action becomes part of the report interface and executes the defined workflow when triggered. Click here to learn more about report workflows.

1. In the project management application, when a team member completes a task listed in the Project Tasks report, a workflow is triggered through the Mark as Completed action item to update the task status, log the completion time, and notify the project manager.
   
2. Within the recruitment application, when an HR staff selects multiple candidates from the Shortlisted Applicants report, the Generate Offer Letter action item triggers a workflow that creates personalized, formatted offer letters and emails them to each candidate individually.
   
3. In the sales management application, when a sales representative selects a lead from the Sales Leads report, the Schedule Follow-up action item opens a form to set the next meeting date and triggers a workflow that adds the follow-up to their calendar.
   

Key benefits

1. Custom actions: Create custom actions specific to your workflow needs beyond the default report, such as edit, delete, duplicate, and view record.
   
2. Direct Execution: Instantly trigger a workflow from the report interface using a configured action item that appears as a button or menu option in the quick view or detailed view of a record.
   
3. Efficiency: Reduce manual steps and ensure consistent execution of complex business logic.
   
   

3.1.8. Functions 

Functions are reusable blocks of Deluge, Java, or Node.js statements that can be invoked from anywhere across applications in your Zoho Creator account. They help modularize logic, reduce redundancy by serving as a centralized hub for complex operations, and improve maintainability. Java and Node.js functions are referred to as cloud functions since they are managed in the cloud environment and support integration with external libraries. These cloud functions also enable connectivity with legacy systems or third-party platforms, making them ideal for bridging modern apps with existing infrastructure. Functions can be invoked from workflows within the same application or from any other application using Deluge scripts. Click here to learn more about functions.

1. In the Creator CRM application, when a new customer is added, a function is triggered to check for duplicates across multiple applications and assign a unique customer ID.
   
2. In the finance application, a function that calculates tax based on region and amount is defined centrally and reused across the Invoice, Purchase Order, and Expense Tracker applications across the creator account to ensure consistent tax computation.
   
3. In the employee management application, employee details are maintained within a function that can be invoked from other applications. This ensures consistent and real-time access to information such as name, designation, and department across the system.
   
4. In an inventory management application, a Java cloud function is used to communicate with a legacy warehouse system that only supports SOAP over custom TCP protocols. The function handles the connection, formats the request, and parses the response, enabling Creator to interact with older systems without rewriting or replacing them
   
5. In a compliance tracking application, a Java cloud function converts uploaded word or image files into PDFs using libraries such as Apache POI, Docx4j, or iText. This enables standardized storage and record keeping, ensuring uniformity across document types, and improving audit readiness.
   

Key benefits

1. Code reusability: Define logic once and reuse it across multiple workflows and applications to minimize duplication.
   
2. Logical modularity: Break down complex operations into manageable, organized blocks for improved clarity and maintenance.
   
3. Cross-application access: Access and manipulate data across different applications within your Creator account.
   
   

3.2. Business use cases 

Case 1: Automated customer support ticketing and resolution system

Consider an organization that uses the Zoho Creator Customer support ticketing app to streamline its customer support operations by automating ticket creation, categorization, assignment, resolution tracking, and reporting. The system integrates multiple departments and efficiently handles large volumes of support tickets by leveraging various workflows and functions as described below:

1. Form workflow - On ticket submission: When a customer submits a support ticket through a form, a form workflow is triggered to validate the submitted data, assign a priority based on the issue type, and send a confirmation email containing the ticket number to the customer. The workflow also automatically routes the ticket to the appropriate support team according to the selected category.
   
2. Report workflow - Custom action item: In the ticket report, support agents have access to an action button labeled 'Escalate'. When clicked, this button triggers a report workflow that updates the ticket’s status to 'Escalated,' assigns it to a senior support team member, logs the escalation timestamp, and sends a notification to the relevant manager.
   
3. Batch workflow - Scheduled ticket review: Every night, a batch workflow executes to review all unresolved tickets older than 7 days. The workflow processes tickets in batches of 100, sending reminder notifications to the assigned agents and their supervisors. Additionally, it generates summary reports on pending tickets and escalations for management’s review.
   
4. Functions - Reusing data and cross-app data sharing: Functions are developed to standardize priority calculation based on customer type and issue severity, verify SLA compliance, and fetch customer details from the CRM application. These functions are invoked within form workflows for priority assignment, ticket creation, ticket updates, status transitions, escalation checks, and so on.
   
   

Case 2: Automated vendor onboarding and contract management

Consider an organization that uses a Zoho Creator vendor management app to streamline onboarding new vendors, managing contract approvals, and tracking vendor performance using workflows as shown below.

Form workflow – vendor registration: When a vendor submits their registration details through the vendor application form, a form workflow validates the provided information and sends a confirmation email to the vendor. The vendor status is initially set to pending review.

1. Blueprint – vendor lifecycle management: Blueprints are used to define the stages of vendor onboarding, such as registration, document verification, contract approval, active vendor, and suspended. It controls which actions users can perform at each stage, ensuring that vendors progress through the proper process before becoming active.
   
2. Report workflow – vendor performance review: In the vendor performance report, procurement officers have a custom action button labeled 'Flag for Review'. Clicking this button triggers a report workflow that marks the vendor for further evaluation, sends notification emails to the procurement team, and logs the review request with a timestamp.
   

 3.3. Navigation guide  

4. Points to note 

1. A maximum of 120 workflow action calls (requests) can be executed per minute and per IP address. Only the following actions are considered when calculating this limit:
   
1. Script in the on load form event
   
2. Script in the on user input form event
   
3. Script in the subform add row form event
   
4. Script in the subform delete row form event
   
5. formula field's expression
   
6. Lookup field's filter (when it uses another field in that form)
   
7. Deluge script behind button click (when it's a stateless form)
   
2. The action calls limit for an app in an account is 250 requests per minute. This limit is shared across all users accessing the same action request within the application.
   
3. The action calls limit for a portal in an account is 250 requests per minute. This limit is shared across all portal users accessing the same action request.
   
4. In blueprints, the maximum number of statements that can be executed in one change stage function and execute transition function is 50.
   
1. Info: A statement refers to one task as a whole. For example, the entire 'if' condition will be considered as a single statement
   
5. In Deluge scripts, the maximum number of statements that can be executed in one function is approximately 5000 to 50000, depending on your pricing plan.
   
6. Deluge's data access tasks cannot be used to add, modify, or delete data in integration forms using the workflows.
   
7. System fields in integration forms are not supported in workflows.
   
8. Integration reports cannot be sent as an attachment with Send Mail task in workflows.
   

5. Related topics

1. Form workflows
   
2. Schedule workflows
   
3. Approval workflows