Get Started with FlowRunner
Follow these steps to set up FlowRunner for your organization. The entire process takes about 10-15 minutes.
Installation Overview
Create Account
Sign in with your Microsoft or Google work account
Salesforce Setup
Install the package and connect your org
Install the Add-in or Extension
Install FlowRunner for Outlook from Microsoft Marketplace, or for Gmail from the Chrome Web Store
Create Your FlowRunner Account
Sign up for FlowRunner using your Microsoft or Google work account. The first user from your organization automatically becomes the administrator.
Create AccountInstall Salesforce Package & Connect Org
Install the FlowRunner managed package, then connect your org from the admin dashboard. The package creates the necessary components for secure communication between Salesforce and your inbox — whether your team uses Outlook, Gmail, or both.
Install the FlowRunner managed package
Installation Link
Click below to install in a production Salesforce org (replace "login" with "test" in the URL for Sandbox):
Install Salesforce PackageFlowRunner will become available on the Salesforce AppExchange in the future.
Installation Steps:
- 1 Log in to Salesforce as a System Administrator
- 2 Open the installation URL in your browser
- 3 Select "Install for All Users"
- 4 Click Install and wait for the confirmation message
Configure FlowRunner in the admin dashboard
Once the package is installed, finish setup from the FlowRunner admin dashboard:
2.2.1 Connect Your Salesforce Org
From the FlowRunner admin dashboard, click "Add Production Org" or "Add Sandbox" and authenticate with the Salesforce org where you installed the package.
You'll need to log in with a Salesforce account that has appropriate permissions to authorize connected apps.
2.2.2 Approve Domain Whitelisting
Once your org is connected, the FlowRunner admin dashboard shows a
Complete Setup button. Click it to grant the one-time
approval that lets FlowRunner set the
IframeWhiteListUrlSettings session variables — allowing
flow-runner.com
(and, for Outlook,
outlook.office.com) to securely render your Salesforce Flows.
Important: This is a one-time approval that enables Lightning Out 2.0 to work inside both the Outlook add-in and the Gmail Chrome extension. No manual Salesforce configuration is required — just press the button.
2.2.3 Select Available Flows
After connecting, FlowRunner will retrieve all Screen Flows from your org. Select which flows should be available to your Outlook and Gmail users.
FlowRunner Input Variables
FlowRunner automatically passes context from Outlook or Gmail to your Screen Flows via these input variables. Add them to your flows to receive email and contact data:
FLR_inputContacts
Type: Contact[] (collection)
Contacts returned by your custom Record Lookup flow. You define the matching logic — by email address, domain, or any criteria you choose.
FLR_inputEmailMessage
Type: EmailMessage (SObject)
Contains email metadata: subject, body preview, sender, recipients, and
timestamps. Optionally includes
FLR_ExternalMessageId__c
and
FLR_ExternalThreadId__c if
configured.
FLR_inputUser
Type: User (SObject)
The current Salesforce user. Optionally includes
FLR_TenantId__c and
FLR_UserId__c — the
Microsoft 365 or Google Workspace tenant and user account IDs of the
signed-in user.
Customize the record lookup flow
Flexible Record Lookup
The FlowRunner package includes a customizable auto-launched flow (flowRunnerRecordLookup) that you can modify to match your business needs:
- Match Contacts by email address, name, or any other data you get from the email
- Find Accounts by email domain (e.g., "acme" from "jane@acme.com")
- Look up Leads, Cases, Opportunities, and other standard or custom objects
- Return exactly the records your team needs
The admin dashboard shows whether the lookup flow is installed and active.
Install the Outlook Add-in or Gmail Chrome Extension
The final step is to install FlowRunner in your team's inbox. Pick the client your team uses — or install both. Individual users can install either themselves, or your Microsoft 365 or Google Workspace administrator can deploy organization-wide.
Outlook · Microsoft Marketplace
Install the FlowRunner add-in directly from Microsoft Marketplace (formerly AppSource):
Open in Microsoft MarketplaceFor Individual Outlook Users
- 1 Open Outlook (web, desktop, or mobile)
- 2 Go to Get Add-ins from the ribbon or settings
- 3 Search for "FlowRunner" and click Add
For Microsoft 365 Admins
- 1 Open the Microsoft 365 Admin Center
- 2 Navigate to Integrated Apps
- 3 Click Deploy Add-in and search for FlowRunner
Gmail · Chrome Web Store
Install the FlowRunner Chrome extension to bring Salesforce Flows into Gmail:
Open in Chrome Web StoreFor Individual Gmail Users
- 1 Open the FlowRunner listing on the Chrome Web Store
- 2 Click Add to Chrome and confirm the permissions
- 3 Open Gmail and launch FlowRunner from the extension icon or side panel
For Google Workspace Admins
- 1 Open the Google Admin console
- 2 Go to Devices → Chrome → Apps & extensions
- 3 Add the FlowRunner extension by ID and set it to Force install for your users
Optional Configuration
Demo Flow Template
Get started quickly with our best-practice Flow template. Install it into your org and customize it to your needs.
The template demonstrates how to use the
FLR_inputContacts,
FLR_inputEmailMessage, and
FLR_inputUser variables with common
sales use cases.
Replace "login" with "test" in the URL for Sandbox.
Pre-approve User Access
For a smooth user experience, configure the External Client App (ECA) in Salesforce:
- Set the ECA policy to "Admin Pre-approved"
- Create the "FlowRunner User" permission set and assign it to the ECA
- Assign the permission set to your end users
Custom Fields for FlowRunner
OptionalFlowRunner can populate custom fields on User and EmailMessage objects. Add these fields to unlock additional context in your flows:
User Object
FLR_TenantId__c
Microsoft 365 or Google Workspace tenant ID
FLR_UserId__c
Microsoft or Google user account ID
EmailMessage Object
FLR_ExternalMessageId__c
Outlook or Gmail message ID for API integrations
FLR_ExternalThreadId__c
Conversation/thread ID for email threading
These fields are automatically populated when present. Useful for integrations that need to reference the original Outlook or Gmail message or FlowRunner context.
Get FlowRunner up and running in 15 minutes.
Our team is here to help you get FlowRunner up and running. Don't hesitate to reach out if you have any questions.