Object-Specific Action
An object-specific action is a Salesforce action button that lives on a specific object's pages and operates in the context of a record from that object.
Definition
An object-specific action is a Salesforce action button that lives on a specific object's pages and operates in the context of a record from that object. Users see object-specific actions in the Highlights Panel, on the record's chatter publisher, in the action menu of the related list, and on mobile record pages. The action can create a related record with pre-filled fields, update the current record, log a call, send an email, post to chatter, or launch a screen flow.
Object-specific actions differ from global actions in two ways: they only appear on pages for their parent object, and they inherit the record's context automatically. A Create New Case action on the Account object pre-fills the Case AccountId with the current Account; a Log a Call action attaches the Task to the record the user is viewing. Global actions, by contrast, appear in the global publisher and on the App Launcher and never know what record the user is looking at when invoked.
How object-specific actions speed up record-context workflows
The action types available per object
Object-specific actions come in eight built-in types: Create a Record (default), Log a Call, Send Email, Update a Record, Custom Visualforce, Lightning Component (LWC or Aura), Flow, and Quick Action with predefined values. Salesforce auto-creates default actions like New Case, New Contact, and Log a Call on most standard objects when the org is first provisioned; admins extend these with custom actions that hit specific business processes (Convert to Subscription, Mark as Lost with Reason).
Where the action appears
Object-specific actions show in four places. The Highlights Panel at the top of a record page shows a configurable subset (the rest collapse into a dropdown). The Chatter publisher on the record's chatter feed exposes Log a Call, Send Email, and post-related actions. The Mobile and Lightning Actions section of the page layout controls which actions appear on mobile devices versus the desktop. Some actions also surface in the related list (the Add button on the Cases related list of an Account uses the New Case action by default).
Context fields and pre-defined values
When you create an object-specific action of type Create a Record, the target object gets a Predefined Field Values section. Pre-fill lookup fields, picklist values, default text, or formula-driven values so the user only has to enter the fields that vary. For example, a New Renewal Opportunity action on Account can pre-fill StageName equals Renewal Negotiation, RecordType equals Renewal, and AccountId equals the current Account. Done right, an object-specific action can drop a 12-field new record dialog down to two or three required fields.
Action layouts
Every object-specific action has its own Action Layout (the form the user sees when they click the action). The layout is separate from the regular page layout and contains only the fields the action needs. Build a focused Action Layout for each business process: an Escalate Case action might show just Priority, Reason for Escalation, and Comments, even though the Case page layout has 40 fields. Smaller action layouts increase completion rates and reduce time spent.
Object-specific actions on Flows
Modern Salesforce admins build complex multi-step processes as screen flows and surface them through object-specific actions of type Flow. The action passes the current record ID into the flow as a $RecordId input, and the flow can read fields, ask the user questions, update records, call subflows, and finally show a confirmation screen. This pattern replaces a lot of custom Visualforce and Lightning Component actions that used to require Apex; declarative-first orgs route 80 to 90 percent of complex actions through Flow now.
Limitations and quirks
Each object can have up to 50 actions in total (across all action types). The Highlights Panel shows the first three actions by default; the rest collapse into the More dropdown. Mobile devices show even fewer (typically two) before collapsing. Some action types (Lightning Component) require explicit profile-level access to the underlying component. Object-specific actions inherit the user's profile permissions for the target object; if the user cannot create a Case, the New Case action on Account fails silently or throws an insufficient privileges error.
How to create an object-specific action and add it to the page layout
Create the action from Object Manager, configure its layout, then add it to the page layout's Salesforce Mobile and Lightning Experience Actions section so users see it on the record.
- Open Object Manager and the source object
Setup > Object Manager > [object name] > Buttons, Links, and Actions. Click New Action.
- Configure the action
Set Action Type (Create a Record, Update a Record, Flow, etc.), Target Object (for create actions), Label (the button text), and Name (the API name). Save. Salesforce opens the Action Layout editor.
- Build the action layout
Drag the fields the user needs to fill into the layout. Keep it short. Add Predefined Field Values if any fields should be filled automatically from context.
- Add the action to the page layout
Return to the source object''s Page Layouts area. Edit the layout. In Salesforce Mobile and Lightning Experience Actions, drag the new action into the desired position.
- Save the layout and test as a user
Save the layout. Log in as a user assigned to the layout, navigate to a record, and click the action. Verify the layout shows correctly, predefined values populate, and save completes successfully.
- Actions only appear if they are on the page layout. Creating an action without adding it to the layout leaves it invisible to users. Test on the right record type, since action sections can differ per record type.
- The Highlights Panel shows three actions by default, the rest collapse into More. Put your highest-frequency action in position one or two; anything after that is essentially hidden.
- Predefined field values bypass validation rules during save in some edge cases. Test with the validation rules active so you do not ship an action that surprises users with errors only some of the time.
- Actions inherit user profile permissions for the target object. If the action does not appear or fails for some users, check Profile > Object Settings before debugging the action itself.
Trust & references
Cross-checked against the following references.
- Create Object-Specific Quick ActionsSalesforce Help
- Actions OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Object-Specific Action.
- Actions in Lightning ExperienceSalesforce Help
- QuickAction Metadata ReferenceSalesforce Developers
Hands-on resources to go deeper on Object-Specific Action.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is an Object-Specific Action?
Q2. How does it differ from a Global Action?
Q3. Why use them?
Discussion
Loading discussion…