Flow templates

The full email-to-pipeline motion in one flow: it takes the people on the email you're reading, creates or updates them as Contacts, links them to an Account, and creates an Opportunity with those contacts attached — all pre-filled from the email context, without leaving your inbox.

• Upserts the email participants as Contacts and links them to an Account
• Creates an Opportunity with the contacts added as Contact Roles
• Shows how to use the FLR_inputContacts, FLR_inputEmailMessage, and FLR_inputUser input variables in a real sales use case

Any Screen Flow — a template or one you build yourself — receives the email's context through input variables you declare in Flow Builder. Declare only the ones the Flow needs; FlowRunner fills in the rest at runtime.

• FLR_inputContacts — Contact[] (collection): one Contact per person the user selects on the email.
• FLR_inputEmailMessage — EmailMessage (record): subject, body, sender, recipients, and timestamps of the open email.
• FLR_inputUser — User (record): the Salesforce user running the Flow.
• FLR_inputAttachments — ContentVersion[] (collection): the attachments the user ticks on the email. FlowRunner uploads each ticked file to the org as a Salesforce File owned by that user before the Flow starts, then passes the file references.

FlowRunner reads a Flow's input variables when you add the Flow and when you click Refresh flows on the org in the admin portal. After you add or change one of these variables, click Refresh flows, or the Flow runs without it.

The full field reference for every variable is in the installation guide.