Build the Flow in Salesforce, let users run it from their inbox.
A record-lookup Flow you design decides which Salesforce records appear in the sidebar when an email opens. Screen Flows run the next step, pre-filled from email context. Publish in Flow Builder; every user gets the current version on next load.
Install the managed package in minutes. No credit card.
"FlowRunner was the only way to truly integrate Salesforce into our existing workflow. The plugin works so seamlessly within Outlook that our team barely even needs to log into Salesforce anymore." — Stijn Terhorst, Sales Manager, Het Nationale Theater
You built the process in Salesforce. It works perfectly but your users still won't use it.
Every admin on Salesforce knows the pattern. The objects are modeled. The fields are on the record pages. The validation rules fire. The Screen Flow passes QA. The Flow ships. Three weeks in, the records are stale, the pages never get seen, the Flows are unused, the dashboard has the same gaps it had before.
01
The inbox tax.
Users live in their email inbox. Every click out of the inbox is a tax they will avoid, so the Salesforce tab stays shut.
02
Records go stale.
Custom fields you spent a quarter designing stay blank. Page layouts never get seen. Activity gets logged Friday from memory, or not at all.
03
Dashboards have gaps.
Managers come asking questions. But the gap isn't the implementation. The workflow around it just never reached the user.
Delivery, not duplication. Your Flows run where your users already are.
One lookup Flow decides what the user sees on email open. The Screen Flows you build decide what the user does next.
No new builder. No proprietary scripting. FlowRunner is the surface that brings your Salesforce implementation — your records, custom fields, validation rules, Permission Sets, and Screen Flows — into Outlook and Gmail.
The record-lookup Flow.
What records surface in the sidebar when a user opens an email.
The record-lookup Flow takes the email's context as input — sender, recipients, subject, body, thread ID, message ID, userIDs — and returns whichever Salesforce records matter for that team in the sidebar. Any object, standard or custom. Any filter. The output is completely up to you.
Sales sees matching Opportunities. Support sees open Cases. A project manager sees linked Deliverables from the custom object built last quarter. A success lead sees renewals due this month for the account in thread. Different teams get different match rules from the same FlowRunner install.
When the whole process is "update a field on an existing record," users can edit fields inline in the sidebar — still governed by their Salesforce field-level security. When the process needs more than one step, Screen Flows take over.
The action Flow.
What the user does next, with the email's context pre-filled.
The Screen Flows you already built or always wanted to build — create an opportunity, log a call, qualify a lead, open a case, run an approval — render natively in Outlook or Gmail. Every email participant, the full message, and the user's tenant identity are available as Flow input variables. Endless copy-pasting becomes a thing of the past.
The Flow executes in your Salesforce org under the user's authenticated session, against your data model, with your Permission Sets and validation rules. Publish a change in a Flow and every user runs the new version on next load.
All logic and data stays where you want it, in Salesforce. Stored in your org, governed by your Permission Sets. FlowRunner is the surface that delivers them.
What other FlowRunner customers have built already.
Each pattern below is a piece of your Salesforce implementation reaching your users in the inbox they already work from. If the admin can build it in Flows, FlowRunner can run it from Outlook or Gmail.
Create an opportunity from an inbound email.
Lookup Flow finds the account from the sender domain. A screen element collects amount, stage, close date. The opportunity is created with the email thread linked as an activity.
Log the email to Salesforce with custom fields.
The EmailMessage record is automatically passed as input variable. A screen element lets the user select the related record and edit custom fields like "Category" and "Department" before logging the activity.
Decide exactly what surfaces in the sidebar per team, per object.
The lookup Flow returns Accounts and Contacts for all users, but only returns Opportunities for Sales and Cases for Customer Service. A custom object for reported Malfunctions show for Technical Support.
Use Agentforce.
The full email context is passed into an Agentforce qualification script. Screen elements lets the user confirm BANT. Agentforce routes to the correct queue.
Create a case.
Inbound support emails become cases without copy-paste. Subject and description are pre-filled from the message. A screen element lets the user confirm or edit the details before logging the case.
Run an approval Flow.
Approval requests trigger from the email that prompted them. Requesters see the relevant record details in the sidebar and can submit the approval without leaving their inbox.
Run any custom Flow your org needs.
If it runs in Salesforce as a Screen Flow, it runs in FlowRunner. No feature gap, no supported-list, no Flow elements we cannot render.
Before and after one afternoon of implementing FlowRunner.
| Before FlowRunner | With FlowRunner |
|---|---|
| Users open Outlook. Salesforce waits in another tab, all day. | Users open Outlook. The matched records, the fields that matter, and the next action are already in the sidebar. |
| You designed a record page with all the relevant fields. Users see none of them. | The lookup Flow surfaces the fields that matter for that user and that email. Users update them inline. |
| The qualification Screen Flow you built sits unopened. Activity gets logged Friday from memory, or not at all. | The qualification Flow renders in the sidebar with pre-filled data. |
| "Change the implementation" means re-training every user on new navigation. | Publish a new field, validation rule, or Flow version in Salesforce. The sidebar reflects it for every user on next load. |
| Sidebar add-ins break on shared mailboxes. | We render a Flow, not a view of Salesforce. Less surface, less to break. |
| Sync tools duplicate contacts and stack new data-quality problems on top of the ones you already have. | No sync layer. Every edit runs through your validation rules, Permission Sets, and field-level security — because the edit happens in Salesforce and is performed by your users. |
| Your dashboard has holes. Forecasting is guesswork. The VP asks why the implementation is not delivering. | Your dashboard fills itself as a byproduct of the user's normal day. The implementation is finally being used for what it was built for. |
Get up and running in 15 minutes.
-
1
Install the FlowRunner managed package in Salesforce.
Use the link to the managed package to install it into production (or a sandbox first). The 2GP package delivers four components: an LWC + Aura pair that renders Screen Flows via Lightning Out 2.0, an External Client App for OAuth, one record-lookup template Flow, and one invocable Apex class that returns records as standardized JSON. No triggers, no custom objects storing customer data.
-
2
Deploy the add-in to your users.
Microsoft 365 Admin Center or Google Workspace Marketplace. Deploy by group or individually. No per-user installation, no endpoint change.
-
3
Select Flows and add the FlowRunner (FLR) input variables.
Pick the flows you want from the FlowRunner admin panel. Add the FLR input variables to your flows so the email context is automatically available. Edit your Flows to use these inputs and save. Assign Flows per persona: sales sees "Log Opportunity"; service sees "Create Case".
-
4
Customize the record-lookup Flow.
The record-lookup Flow ships with template logic to match Contacts, Accounts, and Opportunities by sender data. Take control by overriding the Flow and customizing it to your exact needs.
-
5
Users connect their Salesforce account.
Users are auto-logged into the FlowRunner sidebar via SSO. They authorise their Salesforce account with FlowRunner via OAuth once. That's it.
Your emails stay in the inbox. Your records never leave your org. The admin owns the process. We own the delivery.
We speak the language of IT and Compliance departments.
FlowRunner ships as a Salesforce managed package plus an Outlook add-in or Chrome extension for Gmail. Each verified by Microsoft and Google respectively.
For IT. Installs on your terms.
Deploy the add-in via Microsoft 365 Admin Center or Google Workspace Console — by user, group, or domain. Users authorise Salesforce via OAuth. Scopes are documented and auditable from your Salesforce Setup. Authentication uses Microsoft or Google SSO. Verified apps on Microsoft Marketplace and Chrome Web Store.
For Compliance. Runs in your org.
Both Screen Flows and the record-lookup Flow execute in your Salesforce org under the user's authenticated session. Customer record data transits our server but is never persisted. We store only user identities, OAuth tokens (encrypted at rest, row-level tenant isolation), and run metadata for audit. Error telemetry is PII-scrubbed.
For Admins. Uninstalls cleanly.
There is no technical dependency on FlowRunner. Your data stays where it always was. Your Flows are still in Salesforce.
Hosted on Azure in your region of choice. EU tenancy for EU customers. Data Processing Agreement available. ISO 27001 in progress. GDPR-aligned by architecture: no PII data persistence on our side.
"Salesforce is incredibly powerful, but its biggest pitfall is that it offers too much. For users without an IT background, it can be overwhelming. FlowRunner solves this by stripping away the noise, ensuring our team only sees the information and buttons they actually need to do their job."
Admin-technical questions, answered.
What gets installed in my Salesforce org?
Is this a managed package or an unmanaged package?
Do I control access with Permission Sets?
Where does OAuth live, and what scopes does it request?
Where does record data live?
Can I run FlowRunner alongside another Outlook or Gmail integration?
Does the Gmail add-in have feature parity with the Outlook add-in?
What about data residency? Can I keep data in the EU?
How do I uninstall?
What if my Flow needs a specific input that is not in the email?
Your Salesforce deserves to get used. Let's make that happen.
14-day free trial, no credit card, full feature access. Or book a 30-minute working demo.
€6 per user per month, €50 per org per month. One plan. Everything included. Uninstall tomorrow if it is not a fit. Your objects, fields, Flows, data — all stay exactly where they were.