Creating a Global Action is a Setup workflow: pick the type, configure the target and predefined values, build the layout, add to publishers. The whole process takes 10 to 15 minutes for a typical action.
- Open Global Actions in Setup
Setup, Quick Find Global Actions, click the link. The page lists existing Global Actions. Click New Action.
- Pick the Action Type
Pick Create a Record, Log a Call, Send Email, Custom Visualforce, Flow, or Lightning Web Component. Action Type cannot be changed after creation.
- Configure the action specifics
For Create a Record, pick the target object. For Flow, pick the Flow. For LWC, pick the component. Set Label, Name, and Icon.
- Set Predefined Field Values
On the action record, Predefined Values tab. Add field-value pairs that auto-set when the action runs. Hidden from the user; reduces input burden.
- Build the Action Layout
On the action record, Layout. Drag fields from the palette into the layout. Only fields in the layout appear when the user runs the action. Predefined values cover the rest.
- Add to the Global Publisher Layout
Setup, Publisher Layouts, edit the default. Drag the new action into the Quick Actions section. Save. The action now appears in the Lightning header plus icon.
- Add to mobile and Lightning Apps if needed
For Mobile: Setup, Mobile Apps, Salesforce Mobile App, Mobile Navigation, add the action. For Utility Bar: Lightning App Builder, edit the app, Utility Bar, add the action.
The kind of action: Create a Record, Log a Call, Send Email, Visualforce, Flow, LWC. Cannot be changed after creation.
Display label shown to users. Should describe the action in 1 to 3 words (New Task, Log a Call, Submit Support Request).
API name used in references. Defaults from the Label but must be unique within the org.
The sObject the action creates. Task, Event, Contact, custom objects are all valid.
Visual icon shown next to the label. Pick from the Salesforce Lightning Design System icon library.
- Action Type cannot be changed after creation. Clone the action to switch types.
- Global Actions do not auto-link the new record to the current page context. Use Object-Specific Actions on the page layout when context-linking is needed.
- Predefined Field Values are not validated. A predefined value that violates a Validation Rule fails silently or surfaces a confusing error to the user. Test against the full validation set.
- The Global Publisher Layout limits the number of actions shown directly; overflow goes into a More menu. Order matters; put high-frequency actions first.
- Mobile-specific actions can have different layouts from desktop. Configure both surfaces deliberately rather than expecting a single layout to fit both.