Office 365: Forward Email
Description
Office 365: Forward Email step forwards the email.
Note: To use the step you will need to follow the instructions provided in the Additional notes section.
Permission: Following permissions are required to forward emails:
| Permission type | Permission (from least to most privileged) |
|---|---|
| Delegated | Mail.Send, Mail.ReadWrite |
| Delegated | offline_access |
Configurations
| No. | Field Name | Description |
|---|---|---|
| 1 | Step Name | Name of the step. This name has to be unique in a single workflow. |
| Connection: | For details about app registration, see Office 365 App Registration for Grant Type – Password Grant or Office 365 App Registration for Grant Type Refresh Token | |
| 2 | Grant Type | Select the type of grant from Password Grant or Refresh Token. The data type is string. This field is mandatory. Note: It is recommended to select the grant type from Refresh Token. |
| 3 | Tenant ID | Tenant ID of Microsoft Account. The data type is string. This field is mandatory. |
| 4 | Client ID | Client ID of the Application created in Microsoft Account. The data type is string. This field is mandatory. |
| Client Secret: | ||
| 5 | Accept Value as variable/static | Leave checkbox unchecked to accept Client Secret value from a field in the previous steps of the stream using a drop down list. Else enable checkbox for Client Secret field to appear as Text box. |
| 6 | Client Secret | Specify the Client Secret generated in Microsoft Account. Client Secret is entered using a widget. The widget handles both Text (static value or environment variable) and Combo (drop down containing values from previous steps). If checkbox above is enabled Client Secret field appears as a Text box and accepts static or variable values. Else if checkbox above is disabled Client Secret field appears as a drop down to select fields from previous steps. The data type is secure string. This field is mandatory. |
| 7 | Username | Specify the name of the user whose email attachments are to be downloaded. |
| 8 | Password | Specify the password for the provided user name. |
| 9 | Refresh Token | Specify the refresh token required to authenticate the details. |
| 10 | Button: Test Connection | Test connection with Client ID and Client Secret provided. Verifies whether the connection is established or not. Note: For the purpose of verification fields coming from previous steps are not allowed since field values can only be accessed when workflow is in running state. Static values and environment variables are allowed. |
| General tab: | ||
| General Fields: | ||
| 1 | Message ID To Forward | Provide the message ID to forward. The data type is string. This field is mandatory. |
| 2 | From | Provide an email address of the users from which the email is to be sent. Note: You will not receive an error message even if you provide an invalid email address. |
| Destination Addresses: | ||
| Destination Addresses Fields: | ||
| 1 | To | Provide the email address or semicolon (;) separated email addresses of users to which you want to forward the email. |
| 2 | Cc | Provide the email address or semicolon (;) separated email addresses of users to whom you want to send a carbon copy of the email. |
| 3 | Bcc | Provide the email address or semicolon (;) separated email addresses of users to whom you want to send a blind carbon copy of the email. |
| Message: | ||
| Message Fields: | ||
| 1 | Subject | Provide the subject of the email. |
| 2 | Body | Provide the content of the email. Supported body types: Text or HTML Note: HTML support is provided. However, due to security purposes, it is not recommended to provide the entire HTML body using the environment variable. You can form an HTML body using either Modified Java Script or using an HTML email template. The environment variables or fields can be used at the places of dynamic values in the email template. |
| 3 | Save Draft Email In Case Of Failure | Provide valid input for saving the draft message. Allowed values: Yes or No. Default value: No |
| Inline Images tab: | ||
| Inline Images Fields: | ||
| 1 | Resolve Inline Images by Message Id | Select the checkbox if the inline image reference are solved using message Id. |
| 2 | Message ID | Provide the message ID to resolve inline image references. |
| 3 | Table | Provide the following field details: Content ID: Unique String identifier which uniquely identifies the inline image. Static Image Path: Browse and select the the path of image. Supported file types: .jpg, .jpeg, .png, .svg Variable Image Path: Provide the path of image through previous step field, environment variable. Supported file types: .jpg, .jpeg, .png, .svg |
| Attachments Tab: | ||
| Attachments Fields: | ||
| 1 | Attachment OR Folder Path OR Paths Of Attachments (JSON) | Provide a file path to send a single file as an attachment. OR Provide JSON having paths of multiple files to attach to the mail. OR Provide a folder path to attach all files present in that folder. In this option sub-folders and the files present in those sub-folders will not be attached. |
| Sample JSON: a. Sample JSON for multiple attachments JSON using double slash: {"attachments":[{"filePath":"D:\\Folder\\abc.txt"},{"filePath":"D:\\Folder\\Capture.JPG" }]}b. Sample JSON for Multiple Attachments JSON using forward slash: {"attachments":[{ "filePath":"D:/Folder/abc.txt" },{"filePath":"D:/Folder/Capture.JPG"}]} | ||
| 2 | Browse | Browse for the attachment file. |