Skip to main content

Email Connectors

Email connectors send exports and notifications by mail.

Built-in destinations​

Every team has two built-in email destinations. They appear under Built-in wherever a notification channel picks its connector, and they need no configuration:

  • Reply to sender answers in the thread of the mail that created the upload. It only works for uploads that arrived by email.
  • Forward to email sends to the recipients you enter on the notification channel itself.

Built-in destinations cannot be edited or deleted. They are listed on the Connectors page with a Built-in tag so you can see their delivery history.

Custom email connectors​

Create your own email connector when you want recipients managed centrally, a sender whitelist, or an export destination:

  1. Name - A descriptive name for the connector.
  2. Type - Reply to sender or Forward to addresses.
  3. Email addresses - For Forward to addresses, the default recipients.

A notification channel that uses a custom email connector can override the recipients for that channel. Leave the channel's list empty to use the connector's addresses.

Testing the connection​

  1. Add the connector to the export settings inside a project, or to a notification channel.
  2. Upload a file to the project.
  3. Hit process and check your mailbox.

Best practices​

  • Use Reply to sender to keep notifications in the thread of the original mail.
  • Use Forward to email for uploads that do not arrive by email.
  • For system-to-system delivery, prefer an HTTP connector over email.

Next: Notifications Overview →