Agentforce Apex Actions — @InvocableMethod Guide 2026
🤖 Free Agentforce Course 2026 — sfinterviewpro.com
⚙️ Module 9 of 15
Apex Actions
Custom Code Power
Master Apex for agents — when Flows can't cut it. Performance-critical logic, AI predictions, complex algorithms. Real XYZ win probability calculator. @AuraEnabled invocation. Error handling & best practices. Maximum control. Interview ready!
@Aura
Enabled
Try
Catch
<500
Milliseconds
Max
Control
📍 Course Progress — Module 9 of 15
✅M1
✅M2
✅M3
✅M4
✅M5
✅M6
✅M7
✅M8
M9Apex
M10API
M11Data
M12Deploy
M13Scale
M14Test
M15Done
🎯 What You'll Master in This Module
When to use Apex vs. Flows. @AuraEnabled annotation (making methods invocable). Real win probability calculator with complex logic. Error handling (Try-Catch patterns). Performance best practices (sub-500ms). Org limits & CPU time. Interview patterns. By end, you'll know when code is needed & write production-ready Apex!
Part 1: Apex Fundamentals
What is Apex? When to use. How agents invoke.
Apex Action = custom Java-like code method invoked by agent or Flow. Maximum control. Use when Flows insufficient: complex predictions, performance-critical logic, JSON transformation, bulk operations. Agents pass data — Apex processes — Apex returns result!
1
Flow vs. Apex — Decision Matrix
When to use each
| Scenario | Use Flow? | Use Apex? | Why? |
|---|---|---|---|
| Query records & loop through | ✅ YES | ❌ No | Flow has Query & Loop built-in. Use them! |
| Complex prediction: 10+ factors | ❌ No | ✅ YES | Complex math = Apex. Flow needs 10 Decision boxes! |
| Performance-critical: respond <100ms | ❌ Maybe | ✅ YES | Apex compiled. Flow has interpreter overhead. |
| Transform external API data (JSON) | ❌ No | ✅ YES | Apex handles JSON parsing elegantly. |
| Batch update 5K records | ❌ No | ✅ YES | Apex batch jobs handle bulk. Flow can't. |
✅ Rule of Thumb
Flow First: Can Flow do it visually? Can Flow handle it? Use Flow!Apex When: Flow too slow, too complex, can't do it, or performance is critical.
2
@AuraEnabled: Making Apex Invocable
One annotation unlocks agent access
@AuraEnabled annotation = makes Apex method callable from agents, Flows, & LWCs. Without it = method is hidden. With it = agent can call!
// CORRECT: Method invocable from agents
@AuraEnabled(cacheable=true)
public static CalculationResult predictWin(String oppId) {
// Your logic here
return calculate(oppId);
}
// WRONG: Method NOT invocable (no @AuraEnabled)
public static CalculationResult predictWin(String oppId) {
return calculate(oppId);
}
Interview Questions
Real patterns from Agentforce interviews
| Question | Answer |
|---|---|
| When use Apex vs. Flow? | Flow for multi-step logic, queries, loops. Apex for complex math, performance-critical, JSON transform, bulk ops. |
| @AuraEnabled annotation? | Makes Apex method invocable from agents & LWCs. Without it = hidden. With it = callable! |
| Error handling in Apex? | Try-Catch blocks. Catch exceptions, return safe defaults, log errors. |
| Performance best practices? | Keep execution <500ms. Minimize SOQL queries (use batch). Cache results. |
| Real use case for Apex? | Win probability: stage, days in stage, activity, repeat customer, amount = multiple factors. Apex calculates, returns %. |
Module 9 Summary
Apex mastered
- ✅When to use Apex: Complex predictions, performance-critical, JSON transform, bulk operations.
- ✅@AuraEnabled: Makes method invocable from agents. Mark every public static method agents call!
- ✅Real XYZ Example: Win probability calculator with 5+ factors. Complex math = Apex!
- ✅Error Handling: Try-Catch. Return safe defaults. Never let exceptions bubble up.
- ✅Performance: Target <500ms execution. Minimize DB calls. Cache results.
- ✅Interview Ready: All 5 common Apex questions. Real use cases memorized!
🧠 Module 9 Knowledge Check
Q1: Apex vs. Flow? — Apex for complex, performance-critical. Flow for multi-step, loops, conditionals.
Q2: @AuraEnabled? — Annotation making method invocable from agents. Without it = hidden!
Q3: Win probability example? — Stage (base %) + days in stage + activity + repeat customer + amount = complex logic!
Q4: Error handling? — Try-Catch. Catch exceptions, return safe defaults.
Q5: Performance target? — Keep execution <500ms. Minimize SOQL. Cache results!
☕ Enjoyed this article?
SF Interview Pro is 100% free and maintained by a Salesforce professional. No ads, no paywalls, and no signup required. If this guide helped you prepare for an interview, earn a certification, or grow your Salesforce career, consider buying me a coffee! ☕💜
🇮🇳 UPI (India)
Pay by QR
GPay · PhonePe · Paytm · BHIM
New interview questions every week
Follow for fresh Salesforce Q&A, free courses, and real interview experiences — straight from the trenches.
Follow Us ↗