Object-Specific Action
A Salesforce quick action tied to a specific object that appears on that object's record pages, enabling users to perform contextual actions like creating related records, updating fields, or logging activities directly from the record.
Definition
A Salesforce quick action tied to a specific object that appears on that object's record pages, enabling users to perform contextual actions like creating related records, updating fields, or logging activities directly from the record.
In plain English
“An Object-Specific Action is a Salesforce quick action that's tied to a specific object and appears on that object's record pages. It lets users perform contextual actions like creating a related record, updating fields, or logging an activity directly from the record they're viewing.”
Worked example
The admin at Foxtail Logistics adds an Object-Specific Action called Log Pickup on the Shipment custom object's record page. Drivers click the action button on a Shipment, a focused panel pops up with three fields (Pickup Time, Driver Initials, Pickup Notes), they fill them in, and a related Activity record is created automatically with the Shipment as its parent - all without leaving the Shipment page. The same admin configures a different Object-Specific Action on the Driver object called Log Delivery. Each action only appears on its target object's pages - drivers don't see Log Pickup on a Driver record, only on Shipments.
Why Object-Specific Action matters
An Object-Specific Action is a Salesforce quick action tied to a specific object that appears on that object's record pages, enabling users to perform contextual actions like creating related records, updating fields, or logging activities directly from the record. They're configured per object and appear in places like the highlights panel, mobile cards, and Lightning record pages where users can invoke them without leaving the current record context.
Object-Specific Actions are distinct from Global Actions (which work from anywhere in Salesforce, not tied to a specific object). They're more focused: an Object-Specific Action on Account might create a related Contact, Opportunity, or Case, with the Account record automatically pre-populated. Mature orgs configure object-specific actions thoughtfully to expose the most common workflows from each record type, reducing clicks for routine work.
How to set up Object-Specific Action
Object-Specific Actions are the per-object quick actions on records — "New Contact from Account," "Log a Call on Opportunity." Unlike Global Actions, they inherit the parent record's context — created records auto-link to the parent. Most modern action design uses Object-Specific over Global.
- Open Setup → Object Manager → object → Buttons, Links, and Actions
Object Manager → pick the object → Buttons, Links, and Actions in the left rail.
- Click New Action
Top-right.
- Pick Action Type
Create a Record / Update a Record / Log a Call / Send Email / Custom Visualforce / Lightning Component / Lightning Web Component / Flow.
- For Create: pick Target Object
Often a related child object — "New Case from Contact" creates a Case with the Contact prefilled.
- Set Label, Name, Description, Icon
Action label appears on buttons. Icon from SLDS.
- Configure Action Layout
Drag fields onto the action's mini-form.
- (Optional) set Predefined Field Values with $Source.field references
Object-Specific Actions can reference parent record fields via $Source — "Subject = $Source.Name" copies the parent's name. Global Actions can't do this.
- Save → add to Page Layout
Object Manager → Page Layouts → drag action into Salesforce Mobile and Lightning Experience Actions section. Required for visibility.
Create / Update / Log a Call / Send Email / Custom UI.
For Create — what gets created.
Reference parent record fields. Object-Specific only.
Required for visibility.
- Object-Specific Actions DO inherit parent record context — that's the whole point. Use them when the new record needs to know who its parent is.
- Lightning Record Pages can override Page Layout actions. If the action isn't appearing after adding to layout, check Lightning App Builder.
- $Source references only work in Object-Specific Actions. Global Actions can't reference current record context.
How organizations use Object-Specific Action
Configures object-specific actions on Account for creating new Opportunities and Cases, pre-populating the Account.
Uses object-specific actions to expose common workflows directly from record pages, reducing navigation.
Treats object-specific action design as part of UX work, picking actions based on actual user needs.
Trust & references
Straight from the source - Salesforce's reference material on Object-Specific Action.
- Global Quick ActionsSalesforce Help
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…