Skip to main content

Email

logo-email.png

Email

Nexla's email connector enables seamless bi-directional data integration, allowing you to effortlessly set up automated data flows that ingest both structured and unstructured data from email sources or automatically send organized data to any email address as attachments. Data detected from incoming emails—whether from structured files or unstructured sources like PDF attachments—is automatically organized into ready-to-use Nexsets, while outbound email flows can deliver curated data insights directly to stakeholders' inboxes.

Ingest Data from Email

Email data sources are a simple way to create flows based on data contained in emails. Simply create an email source, define forwarding rules to the uniquely generated email ID, and activate the data source. Then, Nexla will monitor the email ID for incoming data and map the new data into a new or existing Nexset.

This section provides step-by-step instructions for creating a new Email data source that will allow Nexla to ingest data from your email account and organize it into a ready-to-use Nexset.

  1. To create a new Email data source, after selecting the new data data flow type, select the the Email connector, and click the Add Credential tile. This will open the screen below, where you can configure a new email data source:

Create a New Email Data Source

EmailSource.png

Data Source Name

  1. Enter a name for the email source in the Data Source Name field.

Data Processing & Format

  1. Define which part of the email Nexla should read to detect new data by selecting an option from the Dataset Detection Mode pulldown menu. Expand the boxes below to learn more information about each option.

    Email Attachments (Text)

    Nexla will automatically detect data in email attachments that do not require optical character recognition, including file formats such as AVRO, CSV, EDI, XLSX, XLS, JSON, ORC, Parquet, TSV, XML, etc.

    Email Content

    Nexla will automatically detect data located in tables within the email body.

    Image/PDF Email Attachments

    Nexla will automatically detect data in email attachments that require optical character recognition, such as PDF or image files.

  2. Nexla is automatically configured to detect the format in which each file should be parsed. Optionally, to force all files from this email source to be parsed in a specified format, select the corresponding option from the File Content Format pulldown menu.

    The pre-selected Automatically Detect Format option is appropriate for most use cases, including those in which the email source contains files in more than one format.

Single Schema Detection

Optional
  1. To configure Nexla to detect a single schema when reading data from this email source, select Yes from the Enforce Detection of Single Schema pulldown menu.

    When the detection of a single schema is enforced for this email source, new data will result in the growth of that schema. Newly detected data that is unrelated to the schema will be quarantined for reprocessing.

Generate Email ID

  1. Click the Generate Email ID button to generate a unique email ID for this email source.

  2. Copy the email ID and paste it into Notepad or a similar easily accessible location. This ID will be used to forward emails to Nexla.

    The generated email ID is unique to this email source—a new ID is generated for each email source added to a Nexla account.

Save & Create the Email Source

  1. Click Create in the top-right corner of the screen to save & create the email data source; then, continue to Email Forwarding.

Email Forwarding

  1. Log into the email account that will be used with the data source, and configure the account to forward emails to the generated email ID. See the email provider's documentation for instructions on how to set up email forwarding rules.

    • Once email forwarding is configured, Nexla will scan the source for new email content at fixed intervals, and it will organize newly detected data into one or more Nexsets.

    • Typically, a 10-15 minute delay may occur between an email appearing in the associated email account and ingestion into a Nexset.

Data Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create an email destination in any data flow. For email destinations, Nexset data is delivered to the specified email address as an attachment in the selected format, along with a fully customizable email subject and body.

  1. Click the + icon on the Nexset that will be sent to the email destination, and select the Send to Destination option from the menu.

  2. Select the Email connector from the list of available data destinations. This will open the screen below, where you can configure a new email destination:

    Create a New Email Destination

    EmailDestination.png
  3. Enter a name for the email destination in the Name field and a short, meaningful description in the Description field.

  4. Enter the email address to which the data will be sent in the E-Mail Recipient of Data field.

  5. Select the preferred attachment format from the Data File Format pulldown menu. The Nexset data will be packaged into an attachment in the selected format for delivery to the specified email address. Preview samples of the Nexset data in the selected format are displayed in the panel on the right.

  6. Enter a custom, informative subject line and body for the email in the Subject and E-Mail Body fields, respectively.

    Nexla provides a default email subject line and body text for email destinations, and the destination can be created without customizing these fields. However, entering a custom subject line and body text is recommended to ensure that the recipient can easily recognize & identify the email upon delivery.

  7. Click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured email address, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to the email address until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.