Skip to main content
All CollectionsUsing Navgar for Flows
Enable Emails Within Flows
Enable Emails Within Flows
Markus Taylor avatar
Written by Markus Taylor
Updated over a week ago

Enable Emails within Flows

The ability to leverage external communication via email within Flows is a useful function of the Navgar application.

1. Begin setting up a Flow as you otherwise would (see Creating Flows in Navgar)

2. Once you've identified a place between Flow Tasks that you would like an email to be sent, create a step as an Email (either by toggling the Task entry type to Email or by typing .M (Note: This means you need to type both the period and the M at the same time)) and giving it a name as well as a description if you so choose

nav-email-1.png

3. The Task will appear in line and can be dragged and dropped as you would like. An issue is highlighted because it is just a placeholder right now, there will need to be an Email Template associated to the Email Task. Click the email icon

nav-email-2.png

and select Add Template. If there is one already created, select and proceed to step (insert). Otherwise you will need to create a new Email Template

nav-email-3.png

4. Click +Create new template.

nav-email-4.png

5. Insert the pertinent details for your Email Template

Within this template you will have the opportunity to use Variables for your template. Variables are placeholders within templates that are purposefully generic but are customized to the Flow Instance before it is launched.

Example: I've included text into the Body of my Email. By clicking +New Variable, I am able to add a variable name.

nav-email-7.png

Initiating Launch of a Flow containing an Email is very similar to a normal launch, as you locate and click Launch button. The only difference is, you receive prompts for

  • Recipient of the email

  • Replacing any Variables in the template with the actual language/names/terms the Variable represents

  • Once these are completed, you may launch your Flow and subsequent ones with standardized formatting but bespoken to circumstance

Did this answer your question?