When to use these connectors
To send emails, you need to create an Outbound Email Connection. Etlworks includes connectors for Gmail, Office 365, and a generic outbound email connector.
Read how to send emails in Etlworks.
Create a Connection
Start creating an Outbound Email Connection by opening the Connections window, clicking +, and typing outbound into the filter field in the Select Connection Type gallery, then select one of the available Outbound Email connectors.
Outbound Email for Gmail
Use this connector to configure an outbound email connection for Gmail. The connector uses OAuth2 for authentication.
- User: the user name, for example first.last@yourcompany.com.
- OAuth token: click Sign in with Google to generate an OAuth token that will be used for authentication.
Use Gmail API to send emails
To enable sending emails using the Gmail API, check the Use Gmail API checkbox in the Authentication section (located below the OAuth Token authentication control). After enabling this option, make sure to authenticate by clicking the Sign in with Google button and granting the required permissions.
Google now disables SMTP authentication by default for enhanced security. To continue sending emails using SMTP you can enable SMTP authentication by configuring “Less secure app access” in your Google account settings, though this is strongly discouraged by Google.
Inbound Email for Office 365 (Exchange Online)
Use this connector to configure an outbound email connection for Office 365 (Exchange Online). The connector uses OAuth2 for authentication.
- User: the user name, for example first.last@yourcompany.com.
- OAuth token: click Sign in with Microsoft to generate an OAuth token that will be used for authentication.
- : enable to request OAuth consent on behalf of your organization. The user must be an admin.
- Tenant: enter Azure tenant ID. It is only required when you log in with the guest user.
Use Microsoft Graph API to send emails
To enable sending emails using the Microsoft Graph API, check the Use Microsoft Graph API checkbox in the Authentication section. After enabling this option, authenticate by clicking the Sign in with Microsoft button and granting the required permissions.
Microsoft now disables SMTP authentication by default for enhanced security. To continue sending emails using SMTP, an administrator must explicitly enable SMTP authentication in the Microsoft 365 Admin Center under Users → Active users → (select user) → Mail → Manage email apps → enable Authenticated SMTP. However, Microsoft strongly recommends using Graph API instead.
Switching between Graph API and SMTP requires re-authentication, as different security scopes are required for each method.
Outbound Email
Use this connector to configure outbound email connection for email servers other than Gmail or Office 365 (Exchange Online).
- Host: the outbound email server host.
- Port: the outbound email server port.
- User: the user name, for example first.last@yourcompany.com.
- Password: the password.
- Start TLS: if true, this enables the use of the STARTTLS command (if supported by the server) to switch the Connection to a TLS-protected Connection before issuing any login command.
- Enable SSL: if true, Etlworks will use the SSL port by default.
Common Connection parameters
- From: the from email address.
- To: the to email address.
- CC: the cc email address.
- BCC: the bcc email address.
- Subject: the email subject.
- Message: the message body. If an outbound email Connection is used in a source-destination pair, the message body will be automatically populated as part of the FROM - TO transformation.
- Header: an optional header that will be added before the message body.
- Footer: an optional footer that will be added after the message body.
- Folder: the name of the folder on the email server to copy the message to.
- File: the name of a file to attach to the message.
- Content Type: an optional email content type, for example, text/ HTML.
- Content Encoding: optional character encoding for the message body. Use it when you wish to re-encode the message (for example, to UT-8). No encoding means there will be no additional encoding.
- Properties: additional comma-separated Connection properties in a key-value Format. Read more about JavaMail Connection properties.