Working with emails

Integrator can read emails and email attachments using POP3 and IMAP protocols, and send emails using SMPT. Emails and email attachments can be used as a part of the source to destination transformation, just like databases, files, web services, and social web sites.

Connecting to email servers

Start creating Email connection by opening Connections window, clicking + button and by typing in mail is the filter field in the "Select Connection Type" gallery:

Connection parameters

Inbound email connection

To read data from the mail server you need to specify the following parameters for the Inbound Email connection.

Important: if you are using one of the public email providers, for example GMail, make sure to enable POP3 and IMAP for your account, and make sure that account can be accessed from the "less secure applications" (the official name given by Google to the third party application, rather than registered email clients).

Outbound email connection

To send a emails you need to specify the following parameters for the Outbound Email connection:

Working with outbound emails

Sending emails

In Integrator it possible to send an email notification when flow is been automatically executed by the scheduler.

There is also a designated flow type Send Email. You can use it as a part of the nested flow, when multiple flows are combined in the pipeline, and possible executed conditionally or in the loop.

Step 1 Create outbound email connection.

Step 2 Continue by opening the Flow Builder window, clicking the + button and typing email in the Select Flow Type box. Select Send Email flow type.

email flow

Step 3 Select outbound email connection, created in step 1.

Step 4 Select Parameters tab end enter email parameters. most of them are optional override corresponding outbound email connection parameters:

Using outbound email as a destination in the source to destination transformation

Emails and email attachments can be used as a destination in the source to destination transformation, just like databases, files, web services, and social web sites.

Step 1 Create outbound email connection, which will be used as a destination.

Step 2 Create any database, file, web services, or social web site connection, which will be used as a source.

Step 3 Start creating flow in the Flow Builder window by clicking + button and selecting any flow type, where the source is a database, file, web service or social web site and the destination is a file.

Step 4 Modify flow by selecting connection created in step 2 as a source (FROM), and connection created in step 1 as a destination (TO).

Step 5 Add mapping and modify parameters if needed.

Working with inbound emails

Browsing inbound emails

In Integrator you can browse inbound emails for the configured inbound email connection in the Explorer.

browse emails

Using inbound email as a source in the source to destination transformation

Emails and email attachments can be used as a source in the source to destination transformation, just like databases, files, web services, and social web sites.

Step 1 Create inbound email connection, which will be used as a source.

Step 2 Create any database, file, web services, or social web site connection, which will be used as a destination.

Step 3 Start creating flow in the Flow Builder window by clicking + button and selecting any flow type, where the source is a file and the destination is a database, file, web service or social web site.

Step 4 Modify flow by selecting connection created in step 1 as a source (FROM), and connection created in step 2 as a destination (TO). Use appropriate formats for the source and destination.

Step 5 Use field From to define an email subject. Important: use wildcards if needed. If there are multiple matching emails Integrator will select the first one based on a timestamp when email was received.

email subject

Step 6 Add mapping and modify parameters if needed.

Important:

Copying content of the email or attachment to the file

Step 1 Create inbound email connection, which will be used as a source.

Step 2 Create connection, which will be used as a destination. Supported types of the destination connections:

Cloud storages

File storages

Key-value storage

HTTP

Step 3 Start creating flow in the Flow Builder window by clicking + button and selecting Copy Files flow type.

Step 4 Modify flow by selecting connection created in step 1 as a source (FROM), and connection created in step 2 as a destination (TO).

Step 5 Use field From to define an email subject. Important: use wildcards if needed. If there are multiple matching emails Integrator will select the first one based on a timestamp when email was received.

Dumping email attachments to the folder

The simplest way to dump all or matching email attachments to the folder is to use this technique, together with specifying property Dump Attachments To for the inbound email connection. The attachments will be copied to the specified folder in the server storage using original file names.

Filtering inbound emails

Use Filter section when configuring inbound email connection to filter out inbound emails.

filter emails

Available filters

Deleting inbound emails after processing

You can configure connection to automatically delete inbound emails from the INBOX after processing.

Simply enable property Delete inbound emails after reading. This property is disabled by default.

delete emails