Gmail Inbound and Outbound connectors

• Startup
• Business
• Enterprise
• On-Premise
• Add-on

Use Inbound Email for Gmail for reading emails and attachments from Gmail using IMAP protocol. 

Use Outbound Email for Gmail connector for sending emails and attachments from Gmail accounts using SMTP protocol. 

Both connectors support OAuth2 for authentication. 

Gmail premium connector

• Startup
• Business
• Enterprise
• On-Premise
• Add-on

About Gmail connector

Etlworks Gmail connector allows fast, real-time access to Gmail API. The connector works just like any other database connector.

Etlworks partnered with CData to provide access to Gmail using industry-standard JDBC protocol. Read about CData Gmail connector.

When to use Gmail connector

Use this connector to create Flows that extract data, including messages, users, events, and email attachments from and load data into Gmail using Gmail API.

If all you need is to read and send emails using Gmail as a mail server and the standard email protocols (IMAP and SMTP) are enabled for the Gmail account, then you can use Inbound Email for Gmail connector for reading emails and Outbound Email for Gmail connector for sending emails. Both connectors use OAuth2 for authentication.

Prerequisites

Contact support@etlworks.com to enable Gmail premium connector for your account.

Create a Connection

Step 1. In the Connections window, click +, and type in gmail. Select Gmail(premium) connector.

Step 2. Enter Connection parameters

• Authentication type: the authentication type. The default is OAuth.

When using OAuth2 authentication (default):

• OAuth Token: sign in with Google.

When using Username and password authentication (deprecated by Google):

• User: the user name.
• Password: the password.

Use Other parameters to specify the Connection string options. Read about available Connection string options.

Work with Gmail

Gmail Data Models

Our connector for Gmail APIs as relational tables, views, and stored procedures.

• Gmail REST Data Model 
• Gmail IMAP Data Model 

Stored procedures

Stored procedures are available to complement the data available from the Data Models. It may be necessary to update data available from a view using a stored procedure because the data does not provide for direct, table-like, two-way updates. In these situations, the retrieval of the data is done using the appropriate view or table, while the update is done by calling a stored procedure. Stored procedures take a list of parameters and return back a dataset that contains the collection of tuples that constitute the response.

Read about available stored procedures in the REST and IMAP data models.  

To call stored procure from the SQL Flow or from Before/After SQL use EXEC sp_name params=value. Example:

EXEC GetAttachment AttachmentIds='{AttachmentId}', 
AttachmentFolder='{app.data}', Overwrite=false

Extract data from Gmail

If you plan to extract the email body and attachments, ensure the option IncludeMessage is enabled. It is not enabled by default.

Extracting data from Gmail is similar to extracting data from the relational database.

Step 1. Create Gmail Connection which will be used as a source (FROM).

Step 2. Create a destination Connection, for example, a Connection to the relational database, and if needed, a Format (Format is not needed if the destination is a database or well-known API).

Step 3. Create a Flow where the source is a database and the destination is a Connection created in step 2, for example, a relational database.

Step 4. Add a new source-to-destination transformation.

Step 5. Select the Gmail Connection created in Step 1 as a source Connection and select the data object you are extracting data from.

Step 6. Select TO Connection, Format (if needed), and object (for example, database table) to load data into.

Step 7. Click MAPPING and optionally enter Source query (you don't need a query if you are extracting data from the Gmail data object unconditionally).

Step 8. Optionally define the per-field mapping.

Step 9. Add more transformations if needed.

Load data in Gmail

Loading data in Gmail is similar to loading data into a relational database.

Step 1. Create a source Connection and a Format (if needed).

Step 2. Create a destination Gmail Connection.

Step 3. Create a Flow where the destination is a database.

Step 4. Add new source-to-destination transformation.

Step 5. Select FROM and TO Connections and objects (also a FROM Format if needed).

Step 6. Optionally define the per-field Mapping.

Step 7. Add more transformations if needed.

Browse data in Gmail

You must have an Gmail Connection to browse objects and run SQL queries.

Use the Etlworks Explorer to browse data and metadata in Gmail as well as execute DML and SELECT queries against the Gmail Connection.