Agentforce Standard Actions — Complete Guide 2026
Standard Actions —
Real Salesforce Data for Your Agent
Connect your XYZ Sales Assistant to real Salesforce data using pre-built Standard Actions. No code needed! Your agent will finally retrieve Accounts, Opportunities, and generate AI emails from live data.
1. What Are Standard Actions?
Pre-built Salesforce actions — zero configuration, instant power
Flow Actions (M8) = you build the Flow, agent calls it — for DML and multi-step processes
Apex Actions (M9) = you write Apex @InvocableMethod — for complex logic and SOQL
API Actions (M10) = calls external REST APIs — for non-Salesforce systems
Rule: Always check Standard Actions FIRST before building custom ones. If a Standard Action does what you need — use it. Save custom development for genuinely unique requirements.
2. Complete List of Standard Actions
Know all available actions before choosing which to add
1. Query Records — find Accounts and Opportunities by name
2. Get Record Details — get full Account/Opportunity info
3. Draft or Revise Email — connects XYZ Follow-up Email Prompt Template
4. Summarize Record — instant AI summary of any record
These 4 actions cover 90% of what a sales rep actually needs from an AI assistant.
Opportunity: Name, StageName, Amount, CloseDate, Probability, Description
Contact: FirstName, LastName, Title, Email, Phone
Get Record Details: User says "Tell me everything about ABC Pharma" — deep dive on ONE specific record. Agent typically calls Query Records first to find the record ID, then Get Record Details to fetch full info.
If you don't see the template in the dropdown — verify it's Activated in Prompt Builder (Setup → Prompt Builder → XYZ Follow-up Email → Status: Active).
๐ข Industry: Healthcare
๐ Location: Mumbai, Maharashtra
๐ Phone: +91-22-12345678
๐ฐ Annual Revenue: ₹5,00,00,000
๐ฅ Employees: 500
๐ Notes: Leading pharma manufacturer, key XYZ Company silicone customer since 2019
Is there anything else you'd like to know about ABC Pharma — open opportunities, contacts, or a full summary?
๐ MedTech - Device Seals Annual Contract
• Stage: Negotiation/Review
• Amount: ₹18,00,000
• Close Date: 15 June 2026
• Probability: 80%
This deal looks strong at 80% probability! Would you like me to draft a follow-up email to Priya Sharma to move it forward?
Subject: Following Up — Device Seals Annual Contract
Dear Priya,
I hope you're doing well. I wanted to follow up on our ongoing discussion regarding the Device Seals Annual Contract for MedTech Solutions India.
We're in the final stages and I'm confident we can finalize the ₹18,00,000 partnership that supports your medical device production needs. As we're targeting June 15th, would you be available for a brief call this week to review the final terms?
Best regards,
XYZ Company Sales Team
Would you like me to adjust the tone, add anything, or send this email?
BioLife Research is a Hyderabad-based biotechnology research company with 80 employees, currently categorized as a Prospect in our system.
They have one active opportunity — an Initial Trial Order worth ₹3,50,000 (Qualification stage, 30% probability) for pharma-grade silicone tubing for lab testing. This is an early-stage relationship with significant expansion potential if the trial is successful.
Suggested talking points: Understand their specific lab tubing requirements, discuss certification/compliance needs for biotech, position XYZ as a pharma-grade quality supplier.
Good luck with the call! ๐ค
3. Add Actions to Contact Lookup Topic
Give the Contact Lookup topic real data access too
4. Troubleshooting Standard Actions
Common issues and exact fixes
| Problem | Root Cause | Fix |
|---|---|---|
| Agent doesn't call the action when expected | Action description too vague — AI can't match it to user intent | Make Action description more specific: add "Use when user says..." with exact phrases users might say |
| Query Returns 0 results even though records exist | Record name in test doesn't match exactly, OR user's sharing rules hide it | Try searching by partial name. Check agent runs as the correct user (System Admin in Dev Org should see all records) |
| "Draft or Revise Email" shows no Prompt Templates | Template not activated in Prompt Builder | Setup → Prompt Builder → XYZ Follow-up Email → Click Activate. Status must show Active. |
| Agent calls wrong action for a query | Multiple action descriptions overlap — AI picks the wrong one | Rewrite descriptions to be mutually exclusive. Use "ONLY use this action when..." in descriptions to create clear boundaries. |
| Agent shows raw record data without formatting | Instructions don't specify how to format retrieved data | Add FORMAT RULES to Topic Instructions: "When displaying Account data, use: Company | Industry | City | Phone format" |
| Email draft doesn't include contact name | Contact not linked to the Opportunity, or Prompt Template missing Contact merge fields | Ensure Contacts are linked to Account + Opportunity. Check Prompt Template uses {!$Input:Contact.FirstName} merge fields. |
5. Standard Actions — Interview Questions
Questions interviewers ask about Agentforce Actions
| Interview Question | Best Answer |
|---|---|
| What are Standard Actions in Agentforce? | Pre-built agent capabilities provided by Salesforce — zero code or configuration. Examples: Query Records, Get Record Details, Create Record, Update Record, Send Email, Draft Email (Prompt Template), Summarize Record, Search Knowledge. Always check Standard Actions first before building custom ones. |
| How does an agent decide which Action to call? | The AI reads the Action's Name and Description and selects the one whose description best matches what the user is asking. Specific, clear Action descriptions = correct Action selection. Vague descriptions = wrong Action called or no Action called. |
| What is the difference between Query Records and Get Record Details? | Query Records = search returning multiple matching records (broad search). Get Record Details = full information on ONE specific record by ID. Agents typically call Query Records first to find the record, then Get Record Details for complete information. |
| How do you connect a Prompt Template to an agent? | Add "Draft or Revise Email" Standard Action to the Topic, select the Prompt Template from the dropdown. Agent calls this action when user requests email drafting → action fetches record data → populates merge fields → LLM generates email → returned to user. |
| When would you NOT use Standard Actions? | When Standard Actions can't meet the requirement: complex multi-object SOQL (use Apex), DML with business logic (use Flow), external system calls (use API Actions). Standard Actions cover simple CRUD — use custom actions for complex logic. |
Module 7 Summary
Agent has real data superpowers — biggest upgrade so far!
- ✅Standard Actions — pre-built Salesforce capabilities, zero code, instant power. Always check Standard first!
- ✅10 Standard Actions known — Query Records, Get Record Details, Create/Update Record, Send Email, Draft Email, Summarize, Search Knowledge, Get Related List, Identify Object
- ✅Action 1 Added — "Search Salesforce Records" (Query Records) — finds Accounts, Opportunities, Contacts
- ✅Action 2 Added — "Get Account or Opportunity Info" (Get Record Details) — full record details
- ✅Action 3 Added — "Draft Follow-up Email" — connects XYZ Follow-up Email Prompt Template
- ✅Action 4 Added — "Summarize Account or Deal" — instant AI briefings
- ✅Contact Lookup Topic — also got Query Records action for real contact retrieval
- ✅Live Tested — 4 real conversations with actual Salesforce data, AI-generated email, pre-call briefing
๐ Ready for Module 8?
Next: Flow Actions — Build Autolaunched Flows that your agent can trigger. Create follow-up Tasks, send email notifications, update Opportunity stages, and run multi-step business processes — all from natural language commands. Your agent starts WRITING data, not just reading it!
Module 8: Flow Actions →