Actions are the operations (or API operations) that will take place as a result of the trigger defined in the upstream application. These action you can perform on Gmail by simple drag and drop, data mapping of elements and values from the upstream application trigger, derived values using formulas or desired constant that you may wish to map.
The action that you see below automates what you can do manually on Gmail.
To show you how actions work in Connect iPaaS, we will use the use-case of sending back a confirmation email to a customer who sent a request for help to your company. The trigger event for this action will be the email that was sent.
As shown below, you can Send a Message in your Gmail Account based in response to a trigger event.
Setting up Gmail action in you workflow¶
You will first need to select the action type "Send Message" from the Gmail application connector, as shown in Figure 1. After you have chosen the action type and setup the connection, you will then see a list of configurations to choose from, the following sections explain what each configuration does.
After selecting the action "Send Message", you can continue to choose how you want your email to be sent. The following sections provide more information on each actionable attribute.
Add the email address to which the message will be sent. You can either enter an email address or map the fields in the trigger panel to generate your email address dynamically.
Add subject line of the email to be sent. This one line of text is important as it can often determine whether an email is opened or sent straight to the spam folder.
A textbox where you can build the message that will be sent to the Gmail account. You can also map data from the Trigger Data panel on the right to use data from the trigger event. To learn more about data mapping and transformation for Gmail refer to the [Data Mapping and Transformation Guide]
The carbon copy field is an optional field, which you can add if you want to keep somebody in the loop of the email.
The blind carbon copy is again an optional field, which you can add if you want to keep someone in the email loop without revealing their details.