Follow these steps to set up FlowRunner for your organization. The entire process takes about 10-15 minutes.
Sign in with your Microsoft work account
Install the package and connect your org
Install FlowRunner from Microsoft AppSource
Sign up for FlowRunner using your Microsoft work account. The first user from your organization automatically becomes the administrator.
Create AccountInstall the FlowRunner managed package, then connect your org from the admin dashboard. The package creates the necessary components for secure communication between Salesforce and Outlook.
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.
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.
FlowRunner needs permission to set the
IframeWhiteListUrlSettings session variables. This allows the
domains
flow-runner.com and
outlook.office.com
to securely render your Salesforce Flows.
Important: This is a one-time approval that enables Lightning Out 2.0 to work within Outlook.
After connecting, FlowRunner will retrieve all Screen Flows from your org. Select which flows should be available to your Outlook users.
FlowRunner automatically passes context from Outlook to your Screen Flows via these input variables. Add them to your flows to receive email and contact data:
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.
Type: EmailMessage (SObject)
Contains email metadata: subject, body preview, sender, recipients, and
timestamps. Optionally includes
FLR_ExternalMessageId__c and
FLR_ExternalThreadId__c if
configured.
Type: User (SObject)
The current Salesforce user. Includes custom fields
FLR_TenantId__c and
FLR_UserId__c for FlowRunner
context.
The FlowRunner package includes a customizable auto-launched flow (flowRunnerRecordLookup) that you can modify to match your business needs:
The admin dashboard shows whether the lookup flow is installed and active.
The final step is to install the FlowRunner add-in from Microsoft AppSource. This can be done by individual users or deployed organization-wide by your Microsoft 365 administrator.
Install FlowRunner directly from the Microsoft AppSource marketplace:
Open in AppSourceGet started quickly with our best-practice Flow template. Import 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.
For a seamless user experience, configure the External Client App (ECA) in Salesforce:
FlowRunner can populate custom fields on User and EmailMessage objects. Add these fields to unlock additional context in your flows:
FLR_TenantId__c
FlowRunner tenant identifier
FLR_UserId__c
FlowRunner user identifier
FLR_ExternalMessageId__c
Outlook 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 message or FlowRunner context.
Our team is here to help you get FlowRunner up and running. Don't hesitate to reach out if you have any questions.