Put your busywork on autopilot with no-code business rules
Build When-If-Then automation rules that trigger across leads, deals, clients, tasks, tickets, proposals, invoices and projects. A visual builder, a template gallery and dry-run testing mean you go from idea to live rule in minutes - no developers required.
- Free trial
- No credit card
- Free onboarding
Automation lifecycle
From trigger to live rule in five steps
- 01
Define trigger
Pick a record type and created or updated
- 02
Set conditions
Match all or any with nine operators
- 03
Choose actions
Notify, assign, create, update or call out
- 04
Test run
Dry-run against real conditions safely
Activate
Go live and watch the execution log
What's inside
Six automation capabilities
Everything a rule needs, from the trigger to the audit trail. Pick any one to jump to the details.
In detail
How each capability works
Triggers & Record Types
Every automation rule starts with a trigger: when a record is created or updated. CrmLeaf supports eight record types - Lead, Deal, Client, Task, Ticket, Proposal, Invoice and Project - so one rules engine covers your entire business workflow. A single rule watches one record type and one event; combine multiple rules to orchestrate cross-module processes.
- Lead
- Deal
- Client
- Task
- Ticket
- Proposal
- Invoice
- Project
How it works
- Pick a record type and an event: created or updated
- Eight record types cover CRM, projects, support and finance
- Each rule watches one type and one event for clarity
- Chain rules to orchestrate multi-step, cross-module workflows
Conditions Builder
After the trigger fires, the if step evaluates one or more conditions before any action runs. Conditions use match-all or match-any logic (AND/OR groups) and work on both standard fields and custom fields. Nine operators - equals, not-equals, greater-than, less-than, contains, is-empty, is-not-empty, changed and changed-to - let you express precise business logic without writing a single line of code.
- Match all (AND)
- Match any (OR)
- Standard fields
- Custom fields
- 9 operators
Operators reference
- Equals / Not-equals - exact match or exclusion
- Greater-than / Less-than - numeric and date comparisons
- Contains - partial text matching
- Is-empty / Is-not-empty - check for missing data
- Changed / Changed-to - detect field transitions on update triggers
Six Actions
When conditions pass, the then step executes one or more of six action types. Actions run in three modes: sequence (run all in order), bailout (stop on first failure) or parallel (run all simultaneously). Emails support placeholder substitution so every message is personalised to the record that triggered the rule.
- In-app notification
- Send email
- Assign owner
- Create follow-up task
- Update a field
- Outbound webhook
Action details
- In-app notification - alert the right person inside CrmLeaf
- Send email - template with placeholder substitution for personalised messages
- Assign owner / assignee - route records to the right team member automatically
- Create follow-up task - spawn a new task linked to the triggering record
- Update a field - change a standard or custom field value on the record
- Outbound webhook - send data to an external URL (SSRF-hardened)
Template Gallery
Start from a library of pre-built rule templates instead of building every automation from scratch. The gallery covers six categories - sales, finance, projects, support, solar and integrations - each with ready-made triggers, conditions and actions that match common workflows. Pick a template, customise the details for your team, test-run it, and activate.
- Sales
- Finance
- Projects
- Support
- Solar
- Integrations
Example templates
- Assign a new lead to the regional sales rep based on location
- Send a payment-received notification when an invoice is updated to "Paid"
- Create a follow-up task when a deal enters the negotiation stage
- Notify the support manager when a ticket priority changes to "Urgent"
- Fire a webhook to your BI tool when a project budget is updated
Execution Log & Safety
Every rule execution writes a detailed log entry - whether the run succeeded, was skipped because conditions didn't match, or was part of a chain. The activity/run-history screen gives you a chronological view of every automation that fired, so troubleshooting is a matter of reading, not guessing.
Safety guardrails run in the background: loop protection detects trigger chains and enforces a maximum chain depth, a mass-update row cap prevents a single rule from changing too many records at once, and per-job time budgets stop runaway executions before they affect performance.
- Execution log
- Skipped/chained tracking
- Loop protection
- Row cap
- Time budgets
Safety guardrails
- Trigger-chain detection stops infinite loops before they start
- Maximum chain depth prevents deeply nested rule cascades
- Mass-update row cap limits how many records a single rule execution can change
- Per-job time budgets terminate long-running actions gracefully
- Every skipped or chained execution is logged for full auditability
Test Run (Dry Run)
Before you activate a rule against live data, run it in dry-run mode. The test-run simulates the trigger event, evaluates every condition and shows exactly which actions would fire - without creating, updating or notifying anything. Use it to catch logic errors, verify condition combinations and confirm the right records would be matched, all from the visual builder.
- Simulated trigger
- Condition evaluation
- Action preview
- No live changes
What dry run shows
- Which conditions matched and which did not
- Which actions would have fired in the chosen mode (sequence, bailout or parallel)
- Whether a chain would have triggered downstream rules
- A pass/fail summary you can review before activating the rule
Connected across CrmLeaf
Automation rules reach every module your team uses
Because triggers cover eight record types and actions include field updates, task creation and webhooks, one rules engine automates workflows across CRM, project management, support and finance - no middleware required.
- CRM & SalesAuto-assign leads, notify reps when deals change stage
- Projects & TasksCreate follow-up tasks when project milestones are reached
- Support & TicketsEscalate high-priority tickets to the right team automatically
- Invoicing & FinanceSend payment confirmations and update statuses on invoice changes
- Outbound WebhooksPush data to Slack, BI tools or any external endpoint
- Proposals & EstimatesNotify stakeholders when a proposal status changes
FAQ
Common questions about CrmLeaf workflow automation
Plans, triggers, loop protection and testing - what teams ask before they switch their first rule on.
No. Workflow automation is a paid add-on that ships turned off. A Super Admin enables the module, and each plan has its own caps on the maximum number of rules, conditions per rule and actions per rule.
Put your busywork on autopilot
Create your first When-If-Then rule from a template, dry-run it, and watch CrmLeaf handle the repetitive work your team used to do by hand.
Workflow Automation is a paid add-on for the CrmLeaf platform.