Use the Send an Email action to send an email from within a flow. The resulting email may contain values referenced using the following variables:
expressions, e.g. @(today()) or @(now())
In the example below, we demonstrate how a clinic might use this action to send an email to staff notifying them that a mother has been registered.
@run.results.due_date references the due date collected at a previous step in the flow.
Create an Email Pipeline
This action is also a super simple way to push a contact’s inquiry to a team member. Simply create a flow that asks for a contact’s name, inquiry and preferred response method, and configure your account to send an email containing that info off to your support feed or Slack channel. Team members will be able to instantly access the ticket via your CRM or Slack feed and respond accordingly.
The variable @run.contact references the name of the contact if you collected it at a previous step, while @run.inquiry and @contact.channel reference the contact’s inquiry and the way they’d like you to respond (SMS, Call, Email), respectively. Note that if a contact’s “Name” field has already been given a value, you may substitute @contact.name or @contact.first_name.
Using your Own Address
By default, we send emails from a Nyaruka support address. If you’d like to add your own address, simply navigate to your account’s settings page and click the email icon.
Here we’re using a Gmail-hosted email address. You’ll want to plugin your email address, host URL, credentials, port and encryption preference.
If you want to link a Gmail address to your Nyaruka account, you’ll need to switch the ‘Allow less secure apps’ setting in your Gmail account’s ‘Connected apps & sites’ page to ‘ON’:
Note that a standard Gmail account is limited to 500 emails per day. Learn more about Gmail’s limits here: