Agentforce Standard Actions — Complete Guide 2026
🤖 Free Agentforce Course 2026 — sfinterviewpro.com
⚙️ Module 7 of 15
Standard Actions
Master CRUD Operations
Deep dive into all 6 Standard Actions your agent needs: Get Record, Query Records, Create Record, Update Record, Send Email, Create Task. Real XYZ Company examples, code patterns, error handling, interview Q&A. Your agent now performs rock-solid CRUD ops on Salesforce data!
6
Standard Actions
100%
No-Code
30+
Code Examples
Interview Ready
All Q&A
📍 Course Progress — Module 7 of 15
✅M1
✅M2
✅M3
✅M4
✅M5
✅M6
M7StdAct
M8Flow
M9Apex
M10API
M11Data
M12Deploy
M13Scale
M14Test
M15Done
🎯 What You'll Master in This Module
All 6 Standard Actions: Get Record (fetch single record), Query Records (SOQL queries), Create Record (new records), Update Record (modify fields), Send Email (automated emails), Create Task (reminders). Real XYZ Company examples. Inputs, outputs, edge cases. Interview patterns. By end, you'll build agents that CRUD like a boss!
Action 1: Get Record — Fetch Single Record
Look up a record by ID or field value. Returns all fields.
Get Record fetches a SINGLE record from Salesforce. Pass object name + Record ID (or field value). Agent gets back all field values. Fastest way to grab Account/Opportunity/Contact details. Zero-code, point-and-click.
1
Get Record: How It Works
Input — Output — Use Cases
| Aspect | Details |
|---|---|
| What it does | Fetches one record by ID or field lookup (e.g., Account by Name, Contact by Email) |
| Input | Object (Account/Opportunity/Contact), Record ID or field/value pair |
| Output | All fields of that record (ID, Name, fields, etc.) |
| Speed | Instant (sub-100ms) |
| Common Use | User says “Tell me about ABC Pharma” — Get Record fetches Account with Name=ABC Pharma, returns all details |
📋 XYZ Company Example: Account Lookup
User Message: “Who is Rajesh at ABC Pharma?”
Agent Action: Get Record (Account where Name = “ABC Pharma”)
Returns: Account ID, Name (ABC Pharma), Industry (Healthcare), Location (Mumbai), Phone, Revenue ($50M), Description, etc.
Next: Agent uses these details to find Contact with LastName=Rajesh at this Account, then responds with info
Agent Action: Get Record (Account where Name = “ABC Pharma”)
Returns: Account ID, Name (ABC Pharma), Industry (Healthcare), Location (Mumbai), Phone, Revenue ($50M), Description, etc.
Next: Agent uses these details to find Contact with LastName=Rajesh at this Account, then responds with info
✅ When to Use Get Record
Simple lookups. Single record retrieval. User asks “Show me Account X” or “What’s Opportunity Y?” If you need multiple records, use Query instead!
2
Get Record Configuration — In Agent Builder
Follow step-by-step
a
Agent Builder — Canvas View — Add Action block
b
Search: “Get Record” (Standard Action)
c
Object: Select “Account”
d
Identifier: Choose “Record ID” OR “Field” (if field, pick field name + value)
e
Test: Pick an Account record from your org. See all fields returned!
✅ Output Available in Agent
Once action completes, all fields are available: {{GetRecordOutput.Name}}, {{GetRecordOutput.Industry}}, etc. Use in prompts, emails, responses!
Action 2: Query Records — Get Multiple Records
Run SOQL queries. Return list of matching records.
Query Records uses SOQL to fetch MULTIPLE records matching criteria. Pass SOQL string, get back list of records. Powerful for “find all open opportunities” or “show me top accounts.” Agent can loop through results or pass to prompt for analysis.
1
Query Records: How It Works
SOQL + Results
| Aspect | Details |
|---|---|
| What it does | Runs SOQL query, returns matching records as list |
| Input | SOQL query string (SELECT ... FROM ... WHERE ...) |
| Output | List of records (0 to 10K records, respects limits) |
| Speed | Depends on data volume. Usually sub-500ms |
| Common Use | Agent: “Find all open Opportunities with amount > 1M” — Query returns list — Agent analyzes & prioritizes |
📋 XYZ Company: Query Open Opportunities
User: “What open opportunities do we have over ₹50 lakh?”
Query:
SELECT Id, Name, Account.Name, Amount, StageName, Probability
FROM Opportunity
WHERE StageName NOT IN (’Closed Won’, ’Closed Lost’)
AND Amount > 5000000
ORDER BY Amount DESC
LIMIT 10
Returns: List of 3-5 open Opps, all > ₹50L, sorted by size
Agent: Displays list & can summarize each with Prompt Builder
Query:
SELECT Id, Name, Account.Name, Amount, StageName, Probability
FROM Opportunity
WHERE StageName NOT IN (’Closed Won’, ’Closed Lost’)
AND Amount > 5000000
ORDER BY Amount DESC
LIMIT 10
Returns: List of 3-5 open Opps, all > ₹50L, sorted by size
Agent: Displays list & can summarize each with Prompt Builder
✅ SOQL Tips for Agents
Keep queries simple & fast. Limit to 10-50 records (don’t fetch 10K). Use indexed fields (Name, Id, Created Date). Filter aggressively. Let Flow or Apex do complex processing!
2
Query Records Configuration
In Agent Builder
a
Agent Builder — Canvas View — Add Action block
b
Search: “Query Records” (Standard Action)
c
SOQL Query: Paste your SOQL string (SELECT...FROM...WHERE...)
d
Test: See results returned as list
📋 Sample SOQL for Agents
Find all Accounts in Healthcare industry:
SELECT Id, Name, Industry, BillingCity, AnnualRevenue FROM Account WHERE Industry = ’Healthcare’ LIMIT 20
Find recent Cases for Accounts:
SELECT Id, CaseNumber, Account.Name, Status, Priority FROM Case WHERE Status != ’Closed’ ORDER BY CreatedDate DESC LIMIT 10
SELECT Id, Name, Industry, BillingCity, AnnualRevenue FROM Account WHERE Industry = ’Healthcare’ LIMIT 20
Find recent Cases for Accounts:
SELECT Id, CaseNumber, Account.Name, Status, Priority FROM Case WHERE Status != ’Closed’ ORDER BY CreatedDate DESC LIMIT 10
✅ Loop Through Results
If query returns 5 Opportunities, agent can loop through each one & invoke Prompt Builder “Opp Summary” for each. Perfect for batch analysis!
Action 3: Create Record — New Records
Create new Account, Opportunity, Case, Lead, Contact, etc.
Create Record creates a NEW record in Salesforce. Pass object name + field values. Agent returns new Record ID. Common: agent creates Case from user request, creates Lead from email, creates Task reminder. Simple, powerful, no code needed.
1
Create Record: How It Works
Input — Fields — Output
| Aspect | Details |
|---|---|
| What it does | Creates 1 new record. Pass required & optional fields. |
| Input | Object (Account/Case/Lead), field values (required: Name, etc.) |
| Output | New Record ID (+ success message) |
| Speed | Instant |
| Common Use | User: “Create a support case for ABC Pharma about tubing defect” — Agent creates Case — returns Case # |
📋 XYZ Company: Create Support Case
User: “ABC Pharma just reported a quality issue with the tubing order”
Agent Action: Create Record (Case)
Object: Case
Fields:
— Subject: “Quality Issue - Tubing Order (from Tubing Agent)”
— Description: “ABC Pharma reported defect in medical grade tubing...”
— Priority: High
— Status: New
— ContactId: [Rajesh at ABC Pharma]
— Origin: Chat
Returns: Case ID (5003x0000001xyz), Case Number (00001234)
Agent Response: “I’ve created Case #00001234 and assigned to Support team. They’ll contact you within 2 hours.”
Agent Action: Create Record (Case)
Object: Case
Fields:
— Subject: “Quality Issue - Tubing Order (from Tubing Agent)”
— Description: “ABC Pharma reported defect in medical grade tubing...”
— Priority: High
— Status: New
— ContactId: [Rajesh at ABC Pharma]
— Origin: Chat
Returns: Case ID (5003x0000001xyz), Case Number (00001234)
Agent Response: “I’ve created Case #00001234 and assigned to Support team. They’ll contact you within 2 hours.”
✅ Validation Rules + Record Types
If you have Validation Rules or Record Type requirements, pass all required fields! Agent will fail gracefully if required field missing. Always test with different Record Types.
2
Create Record Configuration
In Agent Builder
a
Agent Builder — Canvas View — Add Action
b
Search: “Create Record” (Standard)
c
Object: Select “Case” (or Account, Lead, Contact, etc.)
d
Fields: Map required fields (Subject, Description, Priority, Origin, etc.)
e
Test: See new Case ID created!
⚠️ Required Fields = Mandatory
Every object has required fields. Case requires Subject. Account requires Name. Pass them all or Create fails. Check org setup!
Action 4: Update Record — Modify Existing
Change field values on existing records. No code.
Update Record modifies fields on an EXISTING record. Pass Record ID + field values to change. Agent returns success/failure. Common: move Opportunity to next stage, mark Case as closed, update Account status. No code, pure configuration.
1
Update Record: How It Works
Find — Modify — Save
| Aspect | Details |
|---|---|
| What it does | Modifies specific fields on existing record |
| Input | Record ID (required) + fields to update + new values |
| Output | Success (updated count) or Failure (error) |
| Speed | Instant |
| Common Use | Agent: “Move this Opp to Proposal stage” — Update Opportunity StageName — Done! |
📋 XYZ Company: Update Opportunity Stage
User: “We’ve sent proposal to ABC Pharma. Move their tubing opportunity to Proposal stage.”
Agent Action: Update Record (Opportunity)
Record ID: 0063x0000001abc (tubing opp for ABC Pharma)
Fields to Update:
— StageName: “Proposal/Price Quote” (from Qualification)
— NextStep: “Awaiting ABC Pharma feedback on pricing”
— ExpectedRevenue: 2500000 (₹25L)
Returns: Success
Agent: “Moved ABC Pharma tubing opportunity to Proposal stage. Expected revenue: ₹25L.”
Agent Action: Update Record (Opportunity)
Record ID: 0063x0000001abc (tubing opp for ABC Pharma)
Fields to Update:
— StageName: “Proposal/Price Quote” (from Qualification)
— NextStep: “Awaiting ABC Pharma feedback on pricing”
— ExpectedRevenue: 2500000 (₹25L)
Returns: Success
Agent: “Moved ABC Pharma tubing opportunity to Proposal stage. Expected revenue: ₹25L.”
✅ Field Dependencies
Some fields depend on others (e.g., StageName has picklist values). Agent validates before updating. If invalid value, Update fails!
2
Update Record Configuration
In Agent Builder
a
Agent Builder — Add Action block
b
Search: “Update Record”
c
Object: “Opportunity”
d
Record ID: Pass from prior action output or user input
e
Fields: Select StageName, set to “Proposal“
f
Test: See success message!
⚠️ Be Careful with Bulk Updates
Don’t update the same field on 10K records with one action (limits!). If you need bulk updates, use Flow with loop or Apex batch job!
Action 5: Send Email — Automated Emails
Send email from agent. No SMTP setup needed.
Send Email sends email to users from agent. Salesforce handles SMTP. Pass To, Subject, Body. Common: confirmation emails, follow-ups, notifications. Agent can compose email or use Prompt Builder template. Trust Layer protects recipient data.
1
Send Email: How It Works
Simple, powerful, tracked
| Aspect | Details |
|---|---|
| What it does | Sends email. Tracked in Salesforce Activity (if Contact/Lead found) |
| Input | To (email), Subject, Body (HTML or text). Optional: CC, BCC |
| Output | Success (email sent) or Failure |
| Speed | Instant (email queued) |
| Common Use | Agent: Draft email with Prompt Builder — Send Email — Tracking logged |
📋 XYZ Company: Send Follow-Up Email
Scenario: Proposal sent to ABC Pharma 5 days ago. Agent sends follow-up.
Agent Action: Send Email
To: rajesh@abcpharma.com
Subject: “Following Up: XYZ Tubing Proposal (₹25L) — ABC Pharma”
Body: [Composed by Prompt Builder template]
“Hi Rajesh,
We sent the medical-grade tubing proposal (₹25L, 30-day turnaround) 5 days ago. Do you have any questions or feedback?
If you’d like to discuss pricing options or technical specs, I can set up a call.
Looking forward to your thoughts!
— XYZ Sales Team”
Returns: Email sent. Tracked in ABC Pharma Account activity!
Agent Action: Send Email
To: rajesh@abcpharma.com
Subject: “Following Up: XYZ Tubing Proposal (₹25L) — ABC Pharma”
Body: [Composed by Prompt Builder template]
“Hi Rajesh,
We sent the medical-grade tubing proposal (₹25L, 30-day turnaround) 5 days ago. Do you have any questions or feedback?
If you’d like to discuss pricing options or technical specs, I can set up a call.
Looking forward to your thoughts!
— XYZ Sales Team”
Returns: Email sent. Tracked in ABC Pharma Account activity!
✅ Trust Layer Protects Recipients
Even if email is triggered by agent, Trust Layer masks PII. Recipient won’t see internal IDs or sensitive data. Safe!
2
Send Email Configuration
In Agent Builder
a
Agent Builder — Add Action
b
Search: “Send Email”
c
To: Email address or Contact lookup
d
Subject: Type or use {{PromptOutput}} variable
e
Body: Rich text or Prompt Builder output
f
Test: Email sent!
⚠️ Sending Too Many Emails
Salesforce has limits: 5,000 emails per org per day. If agent sends 1 email per user & you have 5K users — you hit limit! Add rate limiting in Flow if needed.
Action 6: Create Task — Reminders & Follow-Ups
Create task assigned to user or team. Automatic reminders.
Create Task creates reminder task assigned to user. Pass Subject, Due Date, Assigned To. Common: agent creates “Follow up with ABC Pharma” task for sales rep. Appears in their task list. Salesforce sends reminders!
1
Create Task: How It Works
Assignment + Reminder
| Aspect | Details |
|---|---|
| What it does | Creates Task assigned to user, with due date & reminders |
| Input | Subject, Due Date, Assigned To (user ID), Priority, Description |
| Output | Task ID (+ success message) |
| Speed | Instant |
| Common Use | Agent: “Create follow-up task for Ankit: Follow up ABC Pharma in 3 days” |
📋 XYZ Company: Create Follow-Up Task
Scenario: Proposal sent to ABC Pharma. Agent creates reminder task for sales rep Ankit.
Agent Action: Create Task
Subject: “FOLLOW UP: ABC Pharma Tubing Proposal (₹25L) — Awaiting Response”
Due Date: Today + 3 days
Assigned To: Ankit Nahar (sales rep)
Priority: High
Description: “Sent medical-grade tubing proposal on [date]. Check for feedback. If no response, call Rajesh at ABC Pharma. Target close: next 7 days.”
Related Record: Account (ABC Pharma)
Returns: Task created, assigned to Ankit
Result: Ankit gets notification, task in his list, Salesforce sends reminder at due date!
Agent Action: Create Task
Subject: “FOLLOW UP: ABC Pharma Tubing Proposal (₹25L) — Awaiting Response”
Due Date: Today + 3 days
Assigned To: Ankit Nahar (sales rep)
Priority: High
Description: “Sent medical-grade tubing proposal on [date]. Check for feedback. If no response, call Rajesh at ABC Pharma. Target close: next 7 days.”
Related Record: Account (ABC Pharma)
Returns: Task created, assigned to Ankit
Result: Ankit gets notification, task in his list, Salesforce sends reminder at due date!
✅ Task = Accountability
Create Task = make sure things don’t fall through cracks. Agent delegates work to humans. Perfect for follow-ups!
2
Create Task Configuration
In Agent Builder
a
Agent Builder — Add Action
b
Search: “Create Task”
c
Subject: “Follow up with ABC Pharma”
d
Due Date: Now + 3 days
e
Assigned To: Ankit (sales rep user ID)
f
Priority: High (optional)
g
Test: Task created in Ankit’s list!
⚠️ Assigned To = Valid User
Must pass valid Salesforce user ID. Can’t assign to contact or invalid user. Check your org user list!
All 6 Standard Actions — Quick Comparison
Side-by-side reference
| Action | Purpose | Input | Output | Speed | Use Case |
|---|---|---|---|---|---|
| Get Record | Fetch single record | Object, Record ID | All fields of record | Instant | Account lookup |
| Query Records | Fetch multiple records | SOQL query | List of records | Sub-500ms | Find all open Opps |
| Create Record | Create new record | Object, field values | New Record ID | Instant | Create Case from request |
| Update Record | Modify existing record | Record ID, new field values | Success/Failure | Instant | Move Opp to next stage |
| Send Email | Send email | To, Subject, Body | Email sent confirmation | Instant (queued) | Follow-up email |
| Create Task | Create reminder | Subject, Due Date, Assigned To | Task ID | Instant | Follow-up task for rep |
Standard Actions — Interview Questions
Real interview patterns
| Question | Answer |
|---|---|
| What’s the difference between Get Record and Query Records? | Get Record: Fetch ONE record by ID (instant, simple). Query Records: Fetch MULTIPLE records matching SOQL criteria (more flexible, returns list). |
| When would you use Create Task instead of just sending email? | Email notifies immediately (one-time). Task creates accountability & appears in user’s task list with due date & reminders. For follow-ups requiring action, use Task! |
| You need to find top 10 accounts by revenue and display details. Which action? | Query Records with SOQL: SELECT Name, Revenue FROM Account WHERE Revenue > X ORDER BY Revenue DESC LIMIT 10 |
| Can you bulk-update 10K records with one Update Record action? | No! Update Record is for single updates. Bulk updates need Flow with loop or Apex batch. Use appropriate tool for scale! |
| Design a workflow: User reports issue — agent creates case — notifies support lead — assigns follow-up task. Which actions? | Create Record (Case), Send Email (to support lead), Create Task (assign to support team lead for follow-up). |
Module 7 Summary — Standard Actions Mastered
What you know now
- ✅Get Record: Fetch single record by ID. Instant. Simple lookups.
- ✅Query Records: Fetch multiple records with SOQL. Flexible filtering. Perfect for analysis.
- ✅Create Record: New records. No code. Pass object & fields.
- ✅Update Record: Modify existing record fields. Single updates (not bulk).
- ✅Send Email: Automated emails with Salesforce SMTP. Tracked. Safe (Trust Layer).
- ✅Create Task: Reminders for users. Due dates. Automatic nudges.
- ✅All 6 are no-code: Configure visually in Agent Builder. No Apex needed!
- ✅Interview Ready: All 5 common questions + answers memorized.
🎉 You're a Standard Actions Expert!
99% of agent workflows use Standard Actions. Get Record + Query + Create + Update + Send Email + Create Task. You can now build production agents without writing code!
🧠 Module 7 — Knowledge Check
Q1: Difference between Get Record & Query Records? — Get: fetch ONE by ID (instant). Query: fetch MULTIPLE matching SOQL (flexible).
Q2: When would you use Create Task vs. Send Email? — Email: one-time notification. Task: accountability + due date + reminders. For follow-ups, use Task.
Q3: Can you bulk-update 10K records with Update Record action? — No! Use Flow with loop or Apex batch. Update Record is single updates only.
Q4: User wants to find all open Opportunities over ₹50L. Which action & SOQL? — Query Records. SOQL: SELECT...FROM Opportunity WHERE StageName NOT IN (“Closed Won”, “Closed Lost”) AND Amount > 5000000 ORDER BY Amount DESC LIMIT 10
Q5: Design: Create Case + Send Email to Support Lead + Create Task. Which actions? — Create Record (Case), Send Email (notification), Create Task (follow-up for team lead).
☕ 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 ↗