Zoho CRM Automation: Workflows, Blueprints and Macros Explained
A practical guide to Zoho CRM automation: how workflows, blueprints, macros, and scoring rules work…
Every sales team reaches the same inflection point: a rep wants to close a deal at a 25% discount, and the only thing standing between a lost opportunity and a margin disaster is an email to a manager who may or may not respond in time. The Zoho CRM approval process replaces that ad-hoc email chain with a structured, auditable workflow that routes deals and discount requests to the right people automatically. This guide covers everything from creating your first approval rule to configuring multi-level chains, defining actions for approve and reject outcomes, and avoiding the configuration mistakes that cause rules to fire on the wrong records or block your team unnecessarily.

The zoho crm approval process is an automation module inside Zoho CRM that intercepts record saves matching defined criteria and places those records in a pending state until a designated approver acts on them. While the record is pending, the assigned user cannot edit it, which prevents reps from working around approvals by modifying values after submission.
Approval processes live under Setup > Automation > Approval Process. Each process is tied to a single module, such as Deals, Leads, Contacts, or any custom module your organisation has created. A single module can have up to five active approval processes running concurrently on Enterprise edition, each targeting a different criteria set.
The core components of every approval process are:
Records that do not match the criteria pass through normally with no interruption. Records that do match are locked and a notification goes to the first approver in the chain.
Not every decision needs an approval gate. Adding one to a low-stakes field creates friction without value. The scenarios below are the clearest candidates for a formal zoho crm approval process.
When deal size crosses a threshold that requires executive visibility or budget sign-off, an approval process enforces that policy consistently. You define the number once in the criteria, and every rep operates under the same rule regardless of who their manager is.
Discount approval is the most common use case. A typical configuration triggers an approval when a custom Discount Percentage field exceeds 10% or 15%, routing the request to the sales manager or finance team. The deal approval workflow in Zoho CRM records who approved the discount and when, creating an audit trail that ad-hoc Slack approvals cannot provide.
Deals with net-60 or net-90 terms, or instalment structures that differ from your standard offering, can be routed to the finance lead before the rep sends a proposal.
If your CRM includes custom modules for vendor contracts, partnership agreements, or capital requests, the approval process works identically there. You are not limited to standard modules.
Avoid building approval rules on fields that change frequently during normal deal progression, such as Close Date or Stage. Records matching those criteria on every save will flood your approvers with repeat notifications and cause legitimate objections from your sales team.
The following walkthrough creates a discount approval rule on the Deals module that fires when a rep sets a Discount Percentage above 15%.
Navigate to Setup > Automation > Approval Process. Click Create Approval Process. Choose Deals from the module dropdown and give the process a descriptive name such as “Deal Discount > 15%”. A clear name matters when you have multiple rules on the same module.
In the Criteria section, set the condition: Discount Percentage > 15. If your discount field is a custom field you created on the Deals module, it appears in the same dropdown alongside standard fields. You can combine multiple conditions using AND or OR logic. For example, Discount Percentage > 15 AND Deal Amount > $10,000 narrows the rule to significant deals only, avoiding approvals for small contracts where the absolute discount value is negligible.
Choose whether the rule fires On Create, On Edit, or On Create and Edit. For discount approvals, On Create and Edit is usually correct, because a rep may add a discount after the initial deal is saved.
In the Approval Details section, add Level 1. Choose the approver type: a specific user, the record owner’s manager (pulled from the user hierarchy), a role, or a field-based approver where a Lookup field on the record points to the designated approver. For most companies, Manager of Record Owner is the right starting point because it scales automatically as your team grows.
Add at least one action for each outcome. A minimal setup updates the Approval Status field to Approved or Rejected and sends an email to the record owner. More advanced setups update multiple fields, trigger webhooks to downstream systems, or create follow-up tasks.
Save the process as inactive first. Use the test procedure described later in this guide before switching it to active.

Multi-level approval in Zoho CRM means a record must be approved sequentially at two or more levels before the final approval actions run. Each level can have a different approver and its own notification settings. The zoho crm multi-level approval configuration adds levels inside the same approval process rather than creating separate processes.
When a record matches the criteria, Level 1 receives the notification. Once Level 1 approves, the record moves to Level 2. If Level 1 rejects, the rejection actions run immediately and the process ends, regardless of how many levels were configured above. This means rejection at any level terminates the chain.
After saving Level 1, click Add Another Level in the Approval Details section. Assign the Level 2 approver using the same options available at Level 1. A typical two-level deal approval workflow routes to the direct sales manager first, then to the VP of Sales for deals above a higher threshold. You achieve this by creating two separate approval processes with different criteria ranges, or by using a single process with two levels where Level 2 is always required regardless of who Level 1 is.
If your process requires sign-off from two people at the same level independently, such as both a sales manager and a finance manager for large deals, you can set Level 1 to require approval from both users. The record remains pending until both have acted. One rejection from either user at a parallel level triggers the rejection path.
If an approver is on leave, Zoho CRM’s approval process does not have a built-in out-of-office delegation. The standard workaround is to configure a fallback approver at each level, either a second user or a role that includes a backup. Some organisations handle this by temporarily reassigning the manager field on the approver’s profile, which redirects all “Manager” type approvals automatically.
Approval actions and rejection actions in the zoho crm approval rules configuration support four types of automations.
| Action Type | Common Use on Approve | Common Use on Reject |
|---|---|---|
| Field Update | Set Approval Status to “Approved”, unlock Discount field | Set Approval Status to “Rejected”, reset Discount to 0 |
| Email Alert | Notify record owner, send deal summary to finance | Notify owner with rejection reason, CC manager |
| Webhook | Push approved deal to quoting system or ERP | Log rejection event in external reporting tool |
| Task | Create a follow-up task to send the proposal | Create a task to call the customer with revised terms |
Field updates on rejection deserve careful thought. Resetting the Discount field to zero forces the rep to re-enter a lower value when resubmitting, which is the correct behaviour. However, if you clear the field entirely rather than setting it to zero, the field appears blank and the rep may not notice it needs to be updated before resubmitting.
Email alerts should include the approver’s comment field as a merge variable. Zoho CRM’s email templates support the ${ApprovalComments} variable, which pulls in whatever text the approver typed when acting. Without this, rejected deal owners receive a notification that says “your deal was rejected” with no explanation.
Before activating a zoho crm approval process in a live environment, test it on a duplicate or sandbox deal to confirm the criteria fire correctly and the actions execute as expected.
Once testing confirms correct behaviour, return to Setup > Automation > Approval Process, find your rule, and toggle the status from Inactive to Active. The rule applies to all matching records saved after activation. Records already in CRM are not retroactively evaluated unless they are edited and saved again after activation.
Sales operations teams sometimes ask whether to use the approval process or a Zoho CRM Blueprint to control deal progression. The two serve different purposes and are not interchangeable.
The approval process is a binary gate: a record either passes or it does not, and an external approver makes that decision. Blueprint is a state machine that defines every stage transition in a process, enforcing which fields must be filled and which actions must be taken before a record can move forward. Blueprint controls the progression sequence; the approval process controls authorisation for a specific condition.
For discount authorisation specifically, the approval process is the right tool. Blueprint is better suited to enforcing deal stage progression, such as requiring a demo to be logged before a deal can move from Qualified to Proposal Sent.
The two can be used together. A Blueprint transition can include an action that triggers re-evaluation of approval criteria, though this requires careful testing to avoid loops.
Setting criteria on a field that changes on nearly every deal save, such as Close Date, means the approval fires repeatedly on the same records. Narrow your criteria to fields that are set intentionally, such as discount or contract value fields.
Approvers who reject a deal typically type a reason in the comments box. If your rejection email alert does not include the ${ApprovalComments} variable, the record owner receives an opaque rejection with no actionable feedback. Always include the comments variable in rejection email templates.
When a rep edits a rejected record and resubmits, the approval process restarts from Level 1. If your Level 1 approver is the rep’s direct manager and the rep changed the value to just below the criteria threshold, the record should no longer match and should pass through without triggering an approval. Test this path explicitly to confirm the criteria evaluation is working as expected after resubmission.
If you assign a role as the approver and that role has no members, or the only member is the record owner (who is automatically excluded from self-approval), the record will enter pending state with no available approver. It will remain stuck until an admin manually acts on it. Audit your role membership before assigning roles as approvers.
On modules where records are edited dozens of times per day, a broadly written approval criteria can create a backlog of pending records faster than your approvers can clear it. If your approvers are receiving more than 10-15 approval notifications per day, revisit your criteria and narrow the trigger conditions.
Can I set up the Zoho CRM approval process on a custom module?
Yes. Custom modules support the approval process in the same way as standard modules. Navigate to Setup, select Automation, then Approval Process, and choose your custom module from the dropdown. The criteria builder and approver configuration options are identical to standard modules such as Deals and Leads.
What happens to a record if the approver rejects it?
The record is unlocked and the rejection actions you configured run, typically a field update to mark the record as rejected and an email to the record owner with any comments the approver entered. The owner can then edit the record and resubmit, which restarts the approval process from Level 1.
Can a non-admin user see who approved a record and when?
Yes. The record’s timeline and audit log in Zoho CRM show each approval and rejection event, the name of the user who acted, the timestamp, and any comment they added. This is visible to anyone with read access to the record, not just administrators.
Is there a limit to how many approval rules I can create per module?
Zoho CRM allows up to 5 active approval processes per module on Enterprise edition and above. On Professional edition, the limit is lower. If you need more than 5 concurrent rules on a single module, consider combining criteria using OR conditions within a single rule rather than creating separate rules for each scenario.
Can the record owner approve their own deal?
No. Zoho CRM prevents the record owner from approving their own record even if their role or user assignment would technically qualify them as an approver. The system automatically skips self-approval and routes to the next eligible approver in the chain or flags the record as pending with no available approver.
Aaxonix designs and configures Zoho CRM approval workflows that match your actual sales policy, including multi-level discount gates, role-based routing, and integration with downstream quoting or finance systems. Book a call to walk through your current process and identify exactly where approval automation will save your team time and protect your margins.
Book a free consultationA well-configured zoho crm approval process removes the informal negotiation that happens around discounts and high-value deals, replacing it with a consistent, documented gate that every rep and manager operates under equally. Start with a single rule on your highest-risk scenario, test it thoroughly, and expand from there once your team is comfortable with the workflow. For hands-on help configuring approval rules or connecting them to your existing Zoho implementation services, the configuration details in this guide give you a solid foundation to work from.
Tell us what you are working through and a senior architect from our team will get back to you with a straight answer, usually within a couple of working days. No bot, no hard sell.
A senior architect will get back to you at , usually within a couple of working days. Worth checking your spam folder, just in case.
Tell us what you are actually trying to do. You will get a straight answer from a senior architect who has done this before, not a sales rep.
A senior architect will get back to you at , usually within a couple of working days. Worth checking your spam folder, just in case.
Ask it now and a senior architect will get back to you, usually within a couple of working days. It goes to our team, not a mailing list.
A senior architect will get back to you at , usually within a couple of working days. Worth checking your spam folder, just in case.