Gmail

Important:  WORKSPACE REQUIRED: The Gmail connector only supports read operations and is intended to retrieve emails from within an organization's Google Workspace (@mybusiness.com). Currently, there is no way to extract an individual user's emails due to an unknown issue with restricted API usage.


Authentication Connection

In order to retrieve emails you will need an account with the Super Admin Role, as only this role can supply the required permissions. Admin SDK Console. You will also need to create an app in the Google Cloud console.


Integration Connection

Every job requires an integration connection for both the source repository connection and the output connection. Also known as input an output connections. Their job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. In repo mode, it will retrieve list items and all of their relevant metadata from a list or library on the specified site. In output mode, the connection will write content and assign the mapped content type (from type mappings), or simply leave the new list item as a Document. Click here for more information on setting up an integration connection.

There are no fields to configure in an integration connection.

Guide to Integration connections

This is used to store and write content alongside its metadata to Google Drive.


Job Configuration

A 3Sixty Job is the process of moving or syncing content (including versions, ACL's, metadata) from one CMS (content management system) to another. Add tasks to your job to have better control over how your data gets migrated. Click here for details on how to set up an integration job.

Guide to Integration jobs

Configuration

Field

Description

Email addresses of users

A tag input for users in the organisations you wish to crawl

Each user's emails will be stored in a folder with their username. So, admin@mycompany.com, will have a folder called admin.

Gmail Query

By default, 3Sixty performs the following query: in:inbox before:<startTime> after:<endTime>. Populating this field will completely override this query. Possible parameters can be found here.

Only retrieve emails with these tag

Tags input for various labels in the user inboxes. Will filter on these labels even if Gmail Query is populated.

Format

There are three available formats:

  • EML: Base EML format. Attachments will be automatically integrated into the body of the document.

  • HTML: The body will be output in html format. Attachments, if included, will also be output under the user's folder.

  • Text: The plain text of each email will be the body of the document. Attachments, if included, will also be output under the user's folder.

Get Attachments

For Html and Text format. Attachments will be processed as individual documents with the type attachment.

  • Each attachment will have the metadata field attachment.messageId to associate it with its message.

Each thread will be given its own folder

Each email in Gmail has a thread id. This option simply prepends this thread id to emails so email threads will be grouped together on output

Include spam and trash

These folders are not searched by default. Checking this will add them to search results.


API Keys

Gmail Connector: Read=true: Write=false: MIP=false

Repo (Read) Specs

Key

Description

Data Type

emails Email addresses of users String

mailQuery

Gmail Query. This will completely override the default date range query.

String

tagFilter

Only retrieve emails with these tags

String

messageFormat

Select a format

 

getAttachments

Retrieve email attachments. Only works in HTML or Text mode.

Boolean

batchThreads

Each email thread fill be given its own folder

Boolean

includeSpamTrash

Includes trash and spam messages (to only retrieve one, use a query)

Boolean


Looking to integrate with Gmail? We can help.