How to Add a Global Action in Salesforce

If your team is still navigating deep into records just to log a call or create a task, you’re losing time every single day.

Salesforce global actions fix that. They sit at the top of every screen, ready to use in one click — no hunting through menus, no object-specific dead ends. You can log a call, send an email, create a contact, or fire off a custom action from anywhere inside Salesforce.

According to Salesforce’s own research, sales teams spend only 34% of their time actually selling — the rest is eaten by admin work, manual data entry, and navigating tools. Global actions are one of the fastest wins you can unlock to flip that ratio.

This guide walks you through exactly how to add a global action in Salesforce, how to configure it properly, and how to make it available to your team across the publisher and mobile app.

What Is a Global Action in Salesforce?

A global action is a shortcut that lets users complete a specific task — like creating a record, logging activity, or sending a message — from anywhere in Salesforce, without needing to be inside a specific record or object.

Unlike object-specific actions that only appear when you’re inside a particular record (like an Account or Opportunity), global actions are available across the entire platform. They show up in the global publisher bar at the top of the page, in the Chatter feed, and on the Salesforce mobile app.

There are four main types of global actions:

Create a Record — Instantly creates a new record like a Contact, Lead, or custom object without navigating to a specific list view.

Log a Call — Captures call details and activity data directly from wherever the user is in the system.

Send Email — Composes and sends an email logged as an activity, accessible from any screen.

Custom Actions — Triggers a Lightning component, Visualforce page, or Flow — giving you full flexibility to automate complex workflows in one click.

Research from Nucleus Research shows that CRM automation delivers an average ROI of $8.71 for every dollar spent, and global actions are one of the most direct ways to put that automation in reach of every user.

Why Global Actions Matter More Than You Think

Before diving into the setup, it’s worth understanding why this is worth your time.

The average sales rep switches between 10+ tools per day. Every time a rep has to stop what they’re doing to navigate into a record just to log an activity, that’s a context switch. Multiply that by a full team, across a full quarter, and you’re looking at thousands of hours of lost productivity.

Global actions reduce friction at the point where most CRM data loss happens — the moment between an interaction and the logging of that interaction. When it takes three steps instead of ten, reps actually do it.

Salesforce reports that companies using CRM automation see a 29% increase in sales revenue and a 34% improvement in forecast accuracy. Global actions are foundational to making that automation accessible in practice, not just in theory.

They’re also critical for mobile users. With the Salesforce mobile app, global actions are often the primary way field teams and remote workers log work on the go. If your global actions aren’t configured correctly, your mobile CRM experience falls apart.

Before You Start: What You Need

You’ll need System Administrator access or a profile with the “Customize Application” permission to create and manage global actions. If you don’t have that, you’ll need to work with your Salesforce admin.

You’ll also want to think through:

What task do you want the action to complete? The clearer you are on this before you start, the faster the setup goes.

Which fields matter? Global actions let you configure predefined field values, so you can pre-fill data that would otherwise require manual entry every time.

Who needs access to it? Global action visibility is controlled by the Publisher Layout, so you’ll need to know which profiles or apps should see the action once it’s live.

How to Add a Global Action in Salesforce: Step-by-Step

Open Setup and Find Global Actions

From the top-right corner of Salesforce, click the gear icon and select Setup. In the Quick Find search box, type “Global Actions” and select Global Actions from the results under the User Interface section.

This opens the Global Actions manager, where you’ll see a list of any existing actions already configured in your org.

Create a New Global Action

Click the New Action button in the top-right corner of the Global Actions page.

You’ll be presented with a form to configure the action. Here’s what each field means and what you should enter:

Action Type — Select from the dropdown. The most common options are:

• Create a Record — for creating new Salesforce records
• Log a Call — for logging call activity
• Send Email — for sending tracked emails
• Custom Visualforce or Lightning Component — for custom workflows

Target Object — This only appears for “Create a Record” actions. Select the object the action will create (e.g., Contact, Lead, Task, or a custom object).

Label — This is the name users will see on the action button. Keep it short, action-oriented, and clear. “Log Call” is better than “Call Logging Activity.”

Name — This auto-populates from the label but can be edited. It’s the API name, so avoid spaces.

Description — Optional but recommended. Helps admins understand the purpose of the action during future org maintenance.

Click Save to move to the next configuration step.

Configure the Action Layout

After saving, Salesforce takes you to the Action Layout Editor for your new global action. This is where you define which fields appear when a user triggers the action.

Think of this like a mini page layout. You want to:

Include only the fields that are necessary. If you’re creating a “Log a Call” action, the user probably only needs Subject, Description, Call Result, and Date/Time. Every unnecessary field is friction that reduces adoption.

Use predefined field values to pre-fill common entries. For example, if you’re creating a “Create Lead” action for a specific campaign, you can pre-fill the Lead Source field with “Outbound Campaign” so reps don’t have to manually select it every time.

To set a predefined value, scroll down to the Predefined Field Values section below the layout, click New, and select the field and value you want to auto-populate.

Save the layout when you’re done configuring fields and predefined values.

Add the Action to the Global Publisher Layout

Creating the action is only half the job. The action won’t appear anywhere until you add it to a Publisher Layout.

Back in Setup, search for “Publisher Layouts” in the Quick Find box and open the Publisher Layouts manager.

Here’s the key distinction: the Global Publisher Layout controls which actions appear in the global publisher bar at the top of Salesforce. If your action isn’t here, it won’t be accessible from the universal header.

Click Edit next to the Global Publisher Layout (or any custom publisher layout you want to modify).

In the layout editor, you’ll see a palette of available actions at the top and a section at the bottom showing what’s currently on the layout. Drag your new global action from the palette into the “Quick Actions in the Salesforce Classic Publisher” or “Salesforce Mobile and Lightning Experience Actions” section, depending on where you want it to appear.

Salesforce recommends keeping the global publisher to seven or fewer actions — research shows that decision fatigue kicks in when users are presented with too many options, leading to lower action adoption rates.

Click Save when done.

Assign the Publisher Layout to Profiles or Apps

By default, the Global Publisher Layout applies to all users and all apps. But if you’ve created a custom publisher layout for a specific profile or app, you’ll need to assign it explicitly.

Still in Publisher Layouts, look for the Publisher Layout Assignment button (usually in the top-right of the page). Click it to open the assignment matrix.

Here you can map specific publisher layouts to specific user profiles. If your sales team should see a different set of global actions than your support team, this is where you configure that.

Click Save on the assignments page.

Test the Global Action

Before rolling out to your team, test the action yourself.

Navigate to the Salesforce home screen or any record page. Look at the header area and find the global publisher bar — it’s typically represented by the plus (+) icon or the activity bar near the top. Click it and confirm your new action appears in the list.

Click the action and verify:

The layout shows only the fields you configured. Any predefined values are auto-populated correctly. The record saves without errors and appears in the expected object list.

Also test the action from the Salesforce mobile app if your team uses it. Mobile global actions are critical for field teams, and a layout that looks great on desktop can be cumbersome on mobile if the field count isn’t controlled.

Advanced Global Action Configurations Worth Knowing

Using Flows Inside Global Actions

One of the most powerful configurations is triggering a Screen Flow from a global action. Instead of just creating a record, a flow-based action can guide users through a multi-step process — like qualifying a new lead, collecting required fields in a structured sequence, or triggering downstream automation.

To use a Flow: when creating the global action, select Flow as the Action Type, then choose the specific Flow from your org. This turns a one-click action into a guided mini-workflow. 67% of high-performing sales teams report using workflow automation to reduce manual data entry, according to Salesforce’s State of Sales report.

Cloning Actions to Speed Up Configuration

If you need multiple similar global actions (for example, separate “Create Lead” actions for different lead sources), you can clone an existing action from the Global Actions manager. Use the dropdown next to an existing action and select Clone. This preserves your layout configuration and predefined values, saving significant setup time.

Mobile-Only vs. Desktop-Only Layouts

Salesforce lets you configure separate action layouts for mobile and desktop. If your team uses the mobile app heavily, navigate to the publisher layout and look at the Salesforce Mobile and Lightning Experience Actions panel separately from the desktop panel. You can assign different field sets and action orders for each environment.

Common Mistakes That Break Global Actions

Not adding the action to the publisher layout. This is the most common issue. Creating the global action in Setup doesn’t automatically make it visible anywhere. You must add it to a publisher layout and save.

Too many fields on the action layout. Every additional field is a reason for a user to abandon the action mid-way. Keep it minimal. You can always capture more data on the full record later.

Forgetting to test on mobile. A global action that works on desktop but breaks or displays incorrectly on the Salesforce mobile app is a significant problem for any team with field reps. Always test both environments before announcing the action to your team.

Not using predefined values. If you’re creating an action for a specific workflow (like logging inbound calls), there’s usually at least one or two fields that will always have the same value. Pre-filling those reduces friction and improves data quality. CRM data quality directly impacts forecast accuracy — Gartner reports that poor data quality costs organizations an average of $12.9 million per year.

Missing profile assignments. If users aren’t seeing an action, check whether they’re assigned a custom publisher layout that doesn’t include the action. The Global Publisher Layout only applies to profiles that haven’t been assigned a custom layout.

How Global Actions Fit Into a Broader Outbound Strategy

Salesforce global actions are excellent at reducing the internal friction of logging and managing CRM activity. But even perfectly configured Salesforce instances can’t generate pipeline on their own.

The companies that scale consistently don’t just log outreach better — they generate more of it. The difference between teams hitting quota and teams chasing it often comes down to outbound volume, targeting precision, and the consistency of their follow-up sequences.

According to InsideSales.com, it takes an average of 18 touches to reach a B2B prospect, and 80% of deals require at least 5 follow-ups after initial contact. Most teams simply don’t have the system capacity to execute at that volume without a dedicated outbound engine.

That’s where a structured LinkedIn outbound and cold email strategy becomes the multiplier on top of a well-configured CRM. When your Salesforce is clean and your outbound sequencing is running in parallel, pipeline generation becomes predictable rather than reactive.

Conclusion

Adding a global action in Salesforce is one of the highest-leverage admin tasks you can complete in under an hour. When configured correctly, it removes the friction that causes reps to skip logging, reduces the admin time eating into selling hours, and makes your CRM data more complete and trustworthy.

The key steps: create the action in Setup, configure your layout with only the fields you actually need, set predefined values to reduce manual entry, add the action to your publisher layout, and test on both desktop and mobile before rolling it out.

The companies with the cleanest CRM data and the most consistently logged activity share one thing in common — they made the right tasks easy. Global actions are a direct path to that.

If you’re optimizing Salesforce to support outbound sales, the next layer is ensuring the pipeline feeding into that CRM is consistent. A well-configured Salesforce without a reliable outbound engine is like having a spotless warehouse with nothing coming in the door.

Book a strategy meeting with SalesSo to see how our complete outbound system — targeting, campaign design, and scaling — generates pipeline that your Salesforce is ready to receive.