Trail Map › Use-Case Catalog › Workflow Automation
⚙️ Automation · Module 08

Workflow Automation: Get the Right Eyes on a Deal Instantly

A "rep" is a salesperson on your team. Right now, your team might rely on a rep remembering to send an update when something important happens. How to build rules that react the instant a record changes — automatically, every time.

4
Tabs
~12 min
Time to Complete
80 pts
Available
1 Badge
Automation Builder

Why workflow automation matters

VP
Val Petrova · VP of Sales

"The moment a deal over $50K moves into Negotiation, I want to know immediately. I don't want to find out at Monday's pipeline review, three days after it mattered most."

A "deal" (also called an Opportunity in SmartLite) is a potential sale you're tracking — a company that might buy from you. "Negotiation" is one stage in the process of closing that sale, where you and the customer are working out final terms.

A "pipeline review" is a regular meeting where a sales team looks at every deal in progress. Waiting for that meeting to hear big news is too slow.

Relying on a rep to remember to send an update breaks down once things get busy. Reps are focused on closing deals, not typing out status updates. Instead, the system should react to the data itself, automatically — that's what "workflow automation" means.

💡
What you'll achieve
Big deals get leadership's attention the instant they hit a condition you set — automatically, every time, with no extra step for the rep.

What's inside a workflow rule

A "record" is any single saved item in the CRM — one Lead, one Opportunity, one Contact. A "Workflow Rule" watches one type of record (called an "object," like Opportunity) for something to happen. When it does, the rule checks a set of conditions. If those conditions match, it runs one or more actions.

PieceWhat it means
Trigger eventWhen the rule should check: ON_CREATE (a new record is made), ON_UPDATE (an existing one changes), or ON_CREATE_UPDATE (either one)
Condition logicALL means every condition must be true. ANY means just one needs to be true. Either way, you're checking a list of field/comparison/value conditions — for example, "amount is greater than 50000"
Field Update actionRuns before the record is saved — it changes the record's data before it's written to the database
Email Alert / Notification / WebhookRun after the record is saved — they never slow down or block the rep's save
✅
Timing matters
Before-save actions can change what actually gets stored — for example, auto-setting a priority field. After-save actions react to what's already been stored — like telling someone about it — but they can't change the record that triggered them.

A rule that's turned off (inactive) is never checked at all. Toggling a rule off is a safe, instant way to pause automation without deleting your setup.

1 Alert the VP on a big deal

Let's build the rule Val Petrova asked for above. A "VP of Sales" is the executive who leads the whole sales team.

Open Workflow RulesGo to Setup → Workflow Rules → New Rule.
Configure the triggerObject: Opportunity · Trigger: On Update (checks the rule whenever a deal changes).
Add conditionsLogic: ALL · amount > 50000 AND stage = "Negotiation" — both must be true.
Add actionsNotification → recipient: the VP's username. Email Alert → pick a saved email template.
Activate and testSave the rule as active, then edit a real (or test) Opportunity so it meets the criteria — confirm the notification and email actually fire.
🎯
Try a Field Update too
Add a second rule that sets a priority__c field to "High" automatically whenever amount > 100000. Notice it applies instantly, before the record is even saved.

Day-to-day: leadership and reps

Get notified automaticallyThe moment a matching deal changes, the notification and email just arrive — nothing to check for manually.

Day-to-day: admins

Add a new rule as new needs come upWhenever leadership wants visibility into a new condition, add another rule instead of asking reps to remember one more thing.
Toggle off instead of deletingPause a rule that's not needed right now by deactivating it — the setup stays in place for later.
🎯
What to try next
Continue to the Approval Processes trail — that's for stopping something before it happens, not just reacting after.

Test what you learned

1. Which type of action runs before the record is saved?
Field Update
Webhook
Email Alert
2. What does setting condition logic to ANY mean?
Every condition must be true (like saying "and")
Just one condition needs to be true (like saying "or")
No conditions are checked — the rule always fires