Actions are productivity shortcuts in Salesforce that allow users to perform common tasks — creating records, logging calls, sending emails — with fewer clicks and in less time. Instead of navigating through multiple screens, users simply click an action button directly from a record page or the global header.
Actions are especially valuable in the Salesforce Mobile App, where speed and minimal navigation are critical.
The Two Main Types of Actions in Salesforce
There are two broad categories of actions in Salesforce:
- Object Specific Actions — tied to a particular object and available on that object’s record pages
- Global Actions — available from anywhere in Salesforce via the global action menu
This guide focuses entirely on object specific actions, which are one of the most important and most exam-tested features for Salesforce Admins.
What Are Object Specific Actions in Salesforce?
Object specific actions in Salesforce are actions scoped to a particular object. They appear in the action bar on record detail pages, letting users perform context-aware tasks — such as creating a related child record or updating specific fields — without leaving the current page.
Example: An object specific action on the Account object might allow a sales rep to create a new Contact directly from an Account record, with the Account Name automatically pre-populated on the Contact.
Important Admin Notes:
- Object specific actions are created in Object Manager → Buttons, Links, and Actions
- After creation, they must be added to the Page Layout under the Mobile and Lightning Actions section to appear on record pages
Where Do Object Specific Actions Appear?
Once added to the page layout, object specific actions surface in:
- The action bar at the top of a record detail page in Lightning Experience
- The overflow menu (dropdown) when more actions exist than the bar can display
- The Salesforce Mobile App action bar on record pages
Key Benefit: Because object specific actions operate in context, any new records they create are automatically associated with the parent record — saving time and reducing data entry errors.
The 8 Types of Object Specific Actions
Salesforce offers a variety of action types to cover nearly every workflow. Understanding each type is essential for effective admin work and for passing the Salesforce Admin certification exam.
Create Records
Creates a new related record automatically linked to the current record. Ideal for creating Contacts from Accounts, or Cases from Contacts.
Update Records
Allows users to quickly edit specific fields on the current record without entering full edit mode. Great for quick status or stage updates.
Log a Call
Lets users document notes about calls, meetings, or interactions related to a specific record. Automatically logs the activity to the record’s activity timeline.
Send Email
Available only on the Case object. Gives support agents access to a simplified email editor linked directly to the case feed for customer communication.
Flow
Launches a Salesforce Flow directly from a record page. Powerful for guided, multi-step automated processes triggered by users.
Lightning Component (Aura)
Uses an Aura component as a custom action in Lightning Experience or the Salesforce Mobile App — suitable for complex custom UI requirements.
Lightning Web Component (LWC)
Uses LWC as either a Screen Quick Action (with a UI modal) or a Headless Quick Action (runs background logic). The modern, performant choice for custom actions.
Custom Visualforce
Uses a Visualforce Page or canvas app as the action interface. The VF page must include the standard controller for the relevant object. Primarily used in legacy implementations.
Critical Exam Point: The Action Type cannot be changed once an action is created. If you select the wrong type, you must delete the action and create a new one from scratch.
Object Specific Actions vs. Global Actions
A frequent point of confusion for Salesforce Admin candidates is the difference between object specific actions and global actions. The comparison below clarifies the key distinctions.
| Feature | Object Specific Actions | Global Actions |
|---|---|---|
| Where Configured | Object Manager → Buttons, Links & Actions | Setup → Global Actions |
| Where It Appears | On that object’s record pages only | Anywhere in Salesforce (global header) |
| Context Awareness | Yes — auto-links to parent record | No — no automatic relationship |
| Creates Related Record | Automatically associated | Must be set manually |
| Added to Layout Via | Page Layout → Mobile & Lightning Actions | Global Publisher Layout |
| Works on Mobile App | Yes | Yes |
| Best For | Record-specific, context-aware workflows | Universal tasks (e.g., log a call from anywhere) |
The golden rule: If the action needs to know which record it belongs to, use an object specific action. If the task stands alone regardless of context, use a global action.
How to Create Object Specific Actions (Step-by-Step)
Let’s walk through the complete process of creating an object specific action using the classic example: a “New Contact” create action on the Account object.
Step 1: Navigate to the Object in Object Manager
- Click the gear icon ⚙️ in Salesforce and select Setup
- In the Quick Find box, type Object Manager and open it
- Click on the Account object (or whichever object you’re targeting)
- In the left sidebar, click Buttons, Links, and Actions
- Click New Action
Step 2: Configure the Action
- Choose Action Type — Select Create a Record from the dropdown (remember: this cannot be changed later)
- Set the Target Object — Choose Contact as the object that will be created
- Enter a Label — Use something descriptive like “New Contact”; the API Name will auto-fill
- Optionally add a Description for documentation purposes
- Click Save — you’ll be taken to the action layout editor
Step 3: Define the Action Layout
- Drag fields onto the layout — Add the fields users need: Name, Email, Phone, etc.
- Keep it to 8 fields or fewer for optimal user efficiency
- Set Predefined Field Values (recommended) — From the action detail page, set values like Account Name to auto-populate. You can then remove those fields from the layout to keep it lean.
Step 4: Add the Action to the Page Layout
- Return to the Account in Object Manager and click Page Layouts
- Open the relevant page layout
- Scroll down to the Mobile and Lightning Actions section
- Drag your new “New Contact” action into that section
- Save the layout
Result: Users on Account record pages will now see a “New Contact” button in the action bar. When clicked, a dialog appears with only the essential fields — and the Account is automatically linked to the new Contact.
Best Practices
Following these best practices ensures your object specific actions are efficient, user-friendly, and maintainable.
- Limit action layout fields to 8 or fewer. Too many fields slow users down and defeat the purpose of a quick action.
- Use predefined field values to auto-populate known data (like the parent record’s ID) and remove those fields from the action layout.
- Write descriptive labels so users immediately understand the action’s purpose (e.g., “Log Support Call” vs. a generic “Log a Call”).
- Always test on mobile. Object specific actions are front-and-center in the Salesforce Mobile App — verify they render and function correctly on mobile devices.
- Audit your action bar regularly. Too many actions create an overwhelming overflow menu. Prioritize the 4–5 most-used actions for easy visibility.
- Use Flows for complex, multi-step processes rather than cramming multi-step logic into a single create or update action.
- Prefer LWC over Visualforce for any new custom action development — it’s faster, more maintainable, and better supported by Salesforce going forward.
Real-World Use Cases
Object specific actions deliver the most value when applied to repetitive, record-related tasks in your users’ daily workflows. Here are practical examples across common Salesforce objects.
Account Object
A sales team adds a “New Opportunity” create action on Account pages, pre-populating Account Name and default Close Date. Sales reps create pipeline deals in seconds without leaving the account record they’re researching.
Opportunity Object
A revenue operations team adds a “Mark Closed Won” update action that sets Stage to “Closed Won” and stamps the Close Date to today — all with a single button click, followed by a confirmation screen built in Flow.
Case Object
A support team uses the built-in Send Email action type on Cases to respond to customers without leaving the case. Combined with email templates, this significantly reduces average handle time for support agents.
Contact Object
An inside sales team adds a “Log Call” action on Contacts with predefined field values and a custom picklist for call outcome, making post-call activity logging fast and consistent across the team.
Custom Objects
A field service company uses a Flow action on a custom Work Order object that guides field technicians through a structured completion checklist before they can mark a job complete — entirely from their mobile device while on-site.
Salesforce Admin Exam Tips
Object specific actions are a regular topic in the Salesforce Administrator Certification exam, particularly within the UI Customization and Productivity and Collaboration sections.
Exam Cheat Sheet
| Topic | What to Remember |
|---|---|
| Where to Create | Object Manager → Buttons, Links, and Actions |
| Where to Activate | Page Layout → Mobile and Lightning Actions section |
| Action Type | Cannot be changed after creation — must delete and recreate |
| Auto-Association | Created records are automatically linked to the parent record |
| Field Limit | Recommended maximum of 8 fields on an action layout |
| Send Email | Only available on the Case object |
| Context | Object specific actions have context; global actions do not |
| Custom Types | Flows, LWC, Aura components can all be used as action types |
Common Exam Scenarios
Scenario 1: A user wants to create a Contact directly from an Account page with the Account Name already filled in. What should an admin create? Answer: An object specific action of type Create a Record with the target object set to Contact, and a predefined field value for Account Name.
Scenario 2: An admin created an object specific action but selected the wrong action type. What must they do? Answer: Delete the action and create a new one. Action Type cannot be changed after saving.
Scenario 3: An admin created an object specific action but it doesn’t appear on the record page. What’s missing? Answer: The action hasn’t been added to the Page Layout under the Mobile and Lightning Actions section.
Frequently Asked Questions
What are object specific actions in Salesforce?
Object specific actions in Salesforce are context-aware shortcuts tied to a particular object. They appear on that object’s record pages and let users perform tasks — like creating related records, updating fields, or logging calls — without navigating away from the current record.
Can I change the action type after creating an object specific action?
No. The action type is locked once the action is saved. If you selected the wrong type, you must delete the existing action and create a new one. This is a frequently tested point on the Salesforce Admin certification exam.
What is the difference between object specific actions and global actions?
Object specific actions are available only on the record pages of the object they belong to and automatically associate new records with the parent. Global actions are available from anywhere in Salesforce via the global header but have no automatic context or record relationship.
How many fields should I add to an object specific action layout?
Salesforce recommends no more than 8 fields. Keeping the layout lean improves user efficiency. Use predefined field values to auto-populate known data and remove those pre-filled fields from the visible layout.
Do object specific actions work on the Salesforce Mobile App?
Yes. Object specific actions appear prominently in the action bar on record detail pages in the Salesforce Mobile App, making them especially valuable for mobile workers and field teams.
What is the Send Email action type in Salesforce?
The Send Email action type is available exclusively on the Case object. It gives support agents a simplified email editor linked directly to the case feed, enabling them to respond to customers from within the case record.
Why isn't my object specific action showing on the record page?
The most common reason is that the action hasn’t been added to the Page Layout. Navigate to Object Manager → Page Layouts for the object, open the relevant layout, and drag the action into the Mobile and Lightning Actions section, then save.
What's the recommended maximum number of fields on an action layout?
Salesforce recommends a maximum of 8 fields. For fields that need a value but won’t often be edited by users, set predefined values instead of including them on the layout.
Wrapping Up
Object specific actions are one of the most practical and impactful tools in a Salesforce Admin’s toolkit. They reduce clicks, speed up data entry, improve mobile usability, and keep users focused on their work — all with zero code required for the most common use cases.
Whether you’re preparing for the Salesforce Administrator Certification or optimizing an existing org, mastering object specific actions is time well spent. From simple create-record shortcuts to complex Flow-driven guided processes, the breadth of what these actions can accomplish is genuinely powerful.
Ready to Get Certified?
Take your Salesforce Admin skills to the next level.
If you found this guide helpful, our Salesforce Admin Certification Course at MyTutorialRack covers every exam topic in depth — with structured lessons, hands-on exercises, and practice tests designed to get you certified with confidence.
- Full Exam
- Curriculum
- Hands-On Exercises
- Practice Tests
- Expert Instructors
- Lifetime Access
