Skip to main content

Email

The Email connection allows you to connect your own email provider via IMAP/SMTP and perform email operations directly in Siesta AI (agents, workflows, automation).

1. Adding an Email Connection​

  1. Open the Connections section.
  2. Click on Add Connection.
  3. In the dialog, select the Email tile.
  4. Continue by clicking the Continue button.

2. Configuring the Email Provider​

After selecting the connection, fill in the configuration details:

  • Name: internal name of the connection in Siesta AI.
  • Provide your Username: login name for the mailbox.
  • Provide your Password: password or app password.
  • Provide your IMAP Host / IMAP Port: server and port for reading mail.
  • Provide your IMAP Encryption: type of encryption (SslOnConnect, StartTls, None, Auto).
  • Provide your SMTP Host / SMTP Port: server and port for sending mail.
  • Provide your SMTP Encryption: type of encryption (SslOnConnect, StartTls, None, Auto).

Email connection configuration form

3. Scopes and Permissions for Functions​

In the Functions section, you set the permissions for individual email actions (scopes/policies):

  • Enabled - the function is activated without further confirmation.
  • Enabled with confirmation - confirmation is required before execution.
  • Disabled - the function is disabled.

Typically, read operations are allowed directly (e.g., SearchEmailsAsync, GetEmailAsync), while riskier write operations run with confirmation (e.g., SendEmailAsync, DeleteEmailAsync, MoveEmailAsync).

Setting scopes for Email connection functions

4. Recommendations​

  • Use a separate service account or app password.
  • Set the minimum necessary permissions for functions (principle of least privilege).
  • For actions that modify data or send emails, prefer the Enabled with confirmation mode.
  • Regularly review which functions are Enabled.

Summary​

The Email connection provides the ability to connect your own email provider via IMAP/SMTP, securely set scopes for individual functions, and control what actions agents and workflows can perform.

Technical Notes​

  • Implementation: The connection provides generic mailbox access over configured mail credentials.
  • Authentication/scopes: uses IMAP/SMTP style server settings and credentials rather than OAuth scopes. The mailbox account determines which folders and send permissions are available.
  • Functions: search emails, read a message, send email, create draft, delete email, update message flags, move messages, and copy messages.
  • Write behavior: sending, deleting, moving, copying, and flag changes alter the mailbox and should require user approval for shared or customer-facing accounts.