Free
- 10 workflow rules per module, 5 active
- No webhooks, Blueprint or approvals
A deal reaches Negotiation and three things should follow: a manager approves the discount, the contract goes out, and finance hears about it. Zoho CRM could do that with a workflow rule, a Blueprint transition, an approval process or Zoho Flow, and which ones you have depends on your edition. The Free edition gets a handful of workflow rules. Blueprint starts at Professional, and approval processes at Enterprise.
From Zoho's edition comparison page. Zoho revises these, so check it before planning around a number.
Pick the module, give the rule a name and a description someone else will understand, and click Next.
A record action (Create, Edit, Create or Edit, Delete), a date or date-time field, a score change, or a note being added or changed. An Edit trigger can watch any field or just the ones you name.
Watch for: the trigger can't be changed once the rule is saved. Getting it wrong means building the rule again.
Conditions are checked in order, and once a record matches one, the rest are skipped. Standard and Professional allow 5 per rule; Enterprise and Ultimate allow 10.
Email notifications, tasks, field updates, tags, webhooks, functions, a new record and more. One instant set can hold up to 5 emails, 5 tasks and 5 field updates, but only one function and one webhook.
Set a delay in minutes, hours or days, up to 5 scheduled actions per rule. A rule needs at least one instant or scheduled action before it will save.
Watch for: the daily email cap. On Standard it's 100 per user or 5,000 a day, whichever is lower.
Workflow conditions and Blueprint transitions decide from what's on the Zoho CRM record. A webhook posts data out to another system, and Zoho Flow moves records between apps with prebuilt triggers and actions. Neither is built to hold a deal at Negotiation until stock in a warehouse system is confirmed, or a contract is signed in another tool.
The dependable way to do it is to put the outside answer on the record: a service that reads the other system and writes the result to a CRM field the Blueprint or rule can test, or a Deluge function that calls the other system's API on Enterprise and up. n-frames builds that lookup, so Zoho's own automation keeps doing the deciding.
Zoho Motivator turns up next to these in Zoho's menus. It's targets and leaderboards on the same activity data, which is useful for sales tracking but isn't automation.
A workflow rule reacts: something changes and it sends an email, updates a field or creates a task. Blueprint controls: it lays out the stages a record moves through, who can move it and what must be filled in at each transition, so people can't skip a step.
Zoho's own scripting language. In Zoho CRM it runs custom functions called from workflow rules, Blueprint and buttons, and handles what the rule builder can't: calculations, conditional branches and calls to other Zoho apps or outside APIs.
Some of it. Zoho's comparison page lists 10 workflow rules per module on the Free edition, 5 of them active. Webhooks start at Standard, Blueprint at Professional, and approval processes and functions as workflow actions at Enterprise.
Yes. A rule can fire on a date field once, every month or every year, and scheduled actions send an email minutes, hours or days after the trigger. Daily email caps apply by edition. For segmented, multi-step drip campaigns, Zoho Campaigns or another email tool does it better than CRM rules.
n-frames builds it against the Zoho CRM API: the lookup that fetches a stock level, contract state or payment status from the other system and writes it to the record, so your existing rules and Blueprint act on it.