Quick Action
A Salesforce action (global or object-specific) that provides users with a shortcut to perform common tasks like creating records, logging calls, sending emails, or updating fields, accessible from action bars and record pages.
Definition
A Salesforce action (global or object-specific) that provides users with a shortcut to perform common tasks like creating records, logging calls, sending emails, or updating fields, accessible from action bars and record pages.
In plain English
“A Quick Action in Salesforce is a shortcut that lets users perform common tasks like creating records, logging calls, or sending emails. Quick actions can be global (available anywhere) or object-specific (tied to a particular record type), appearing in action bars and record pages.”
Worked example
The admin at Vanguard Solutions adds three Quick Actions to the Opportunity page layout: "Log a Call," "Create Quote," and "Schedule Follow-up." A rep working a $500k deal clicks "Log a Call" right after the call ends - a focused side panel pops up asking only for the call's purpose, outcome, and next step, with the Opportunity already pre-filled as the related record. The rep types four lines, hits Save, and is back on the deal page in under fifteen seconds. Without the Quick Action, the same activity log would have meant clicking "New Task," picking a Type, finding the related record - at least eight more clicks on a different page.
Why Quick Action matters
A Quick Action is a Salesforce action (global or object-specific) that provides users with a shortcut to perform common tasks like creating records, logging calls, sending emails, or updating fields, accessible from action bars and record pages. Quick actions support streamlined workflows: instead of navigating to a full create form, users click a quick action and get a focused popup with just the essential fields.
Quick actions are a major productivity feature because they reduce clicks for common workflows. Mature orgs configure quick actions thoughtfully to expose the most common operations from each context: creating related records, logging interactions, updating status. Both global actions (available anywhere) and object-specific actions (appearing on specific record types) have their roles. The challenge is balancing useful actions against action bar clutter.
How to set up Quick Action
Quick Actions are the per-object actions you see on a record's page — "New Task," "Log a Call," "Convert Lead." Object-Specific Quick Actions inherit the parent record's context (creating a Task from an Account auto-fills the Account); Global Actions don't.
- 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 of the actions list.
- 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 the Target Object
Often a related child object — "New Case from Contact" creates a Case with the Contact prefilled.
- Set Label, Name, Description, Icon
Same as Global Actions.
- Configure the Action Layout
Drag fields. The fields drag from the parent object's field set if applicable.
- (Optional) set Predefined Field Values
Auto-populate fields. Can reference parent-record fields via $Source for Object-Specific Actions — Global Actions can't do this.
- Save → add to the Page Layout
Object Manager → object → Page Layouts → drag the action into the Salesforce Mobile and Lightning Experience Actions section. Without this step the action is invisible.
Create / Update / Log a Call / Send Email / Custom. Locked after Save.
For Create actions — child object whose record gets created.
Auto-populate. Object-Specific Actions can reference $Source.field for parent-record context.
Custom UI inside the action modal. Pass record context as a property.
Add the action to the page layout's Mobile and Lightning Experience Actions section. 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.
- Adding to the Page Layout is the step everyone forgets. The action exists in Object Manager but doesn't show up on records until it's on the layout.
- In Lightning, the Lightning Record Page can override the Page Layout's actions section. If you can't get the action to appear after adding to the layout, check the Lightning Page in Lightning App Builder.
How organizations use Quick Action
Built quick actions for logging calls from contact records, streamlining the most common rep workflow.
Uses object-specific quick actions to expose common related-record creation with pre-populated context.
Treats quick action design as part of UX work, avoiding clutter while exposing useful shortcuts.
Trust & references
Straight from the source - Salesforce's reference material on Quick Action.
- Global Quick ActionsSalesforce Help
- Create Object-Specific Quick ActionsSalesforce Help
Test your knowledge
Q1. What is a Quick Action?
Q2. What are the two main types?
Q3. Why use quick actions?
Discussion
Loading discussion…