For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connect a Conversation Platform: Email

Connect the Email channel: set up the mailbox account for receiving and sending (Gmail requires an app-specific password), bind an Agent, and let the Agent reply automatically to incoming emails — ste

Before You Connect

  • An "AI Assistant" has been created on the MaiAgent platform

  • The email account to connect is ready (Gmail, Outlook, Yahoo, or a custom mail server)

  • If you use Gmail or Outlook, generate an app-specific password first (not your account password)

What the Email Channel Does and Doesn't Do

The Email channel works as "receive an email → the Agent replies automatically": MaiAgent uses IMAP to fetch new emails sent to this mailbox, hands them to the bound Agent to generate a reply, and then replies to the sender over SMTP. Every incoming email and reply appears in All Conversations, where support staff can also take over the reply. It does not import existing emails from the mailbox, and users cannot search or query the contents of this mailbox from a conversation.

To search email, summarize messages, or draft replies in a conversation, use MaiGPT Connectors to connect Google Workspace (Gmail) or Microsoft 365 (Outlook). Available connectors depend on your organization's connector menu.

Start Connecting

1. Go to the Connect Channel Page

Click Channels in the left menu, then click the Connect Channel button in the upper right corner.

2. Select Email

On the platform selection page, click Email.

3. Select the Email Provider

Choose from the Email Provider dropdown:

Provider
Description

Gmail

Google mailbox; requires an app-specific password

Outlook / Office 365

Microsoft mailbox; requires an app-specific password when two-step verification is enabled

Yahoo Mail

Yahoo mailbox; requires an app-specific password

Custom

Configure the IMAP/SMTP server parameters yourself

After you select a provider, the system automatically fills in the corresponding IMAP and SMTP server settings.

4. Enter Connection Information

Email Address

Enter the full email address to connect, for example support@yourcompany.com.

IMAP Settings (Receiving)

Field
Description

IMAP Server

Incoming mail server address (imap.gmail.com for Gmail)

IMAP Port

Port number (usually 993)

Use SSL

Recommended, to keep transmission secure

SMTP Settings (Sending)

Field
Description

SMTP Server

Outgoing mail server address (smtp.gmail.com for Gmail)

SMTP Port

Port number (usually 587)

Use TLS

Recommended, to keep transmission secure

Authentication

Field
Description

Username

Usually the email address

Password

App-specific password (not your account password)

5. Test the Connection

After filling in the fields, click the Test Connection button. The system tests both the IMAP (receiving) and SMTP (sending) connections.

  • Connection succeeded: shows "Connection successful! IMAP and SMTP server connection tests passed"

  • Connection failed: the system shows the specific error (authentication failure, server unreachable, etc.); correct the settings accordingly

6. Basic Settings and Save

Field
Description

Channel Name

A name for this connection

AI Assistant

Select the Agent to bind

Polling Interval

(Optional) How often the system checks for new emails (in seconds)

Reset Command

(Optional) A command that lets users start the conversation over

After confirming the settings, click Save to finish connecting.

Once connected, when someone sends an email to that address, the Agent automatically reads the email and replies.

After a successful connection, you can find it in the channel list. Click Edit to configure further options (scheduled replies, sender-name awareness, permission control, and more).

How Incoming Attachments Are Handled

Attachments in incoming emails (including inline images in the HTML body) are saved as attachments of that message and are handled the same way as files a user uploads in Web Chat:

Attachment type
How the Agent reads it

Images (.png, .jpg, .gif, .webp, etc.)

Passed directly to the Agent's language model for interpretation, so the Agent must use a multimodal model; turn on Enable OCR in the feature settings to recognize text in images

Documents (PDF, Word, Excel, CSV, PowerPoint, TXT, and other formats supported by the knowledge base) and audio

The Agent must use Agent mode: based on the email, the Agent decides whether to use the attachment tools to parse the file, read the full text, or build an index, and then replies accordingly. Excel/CSV files are converted to table text so the Agent can answer questions about cell values, and audio is first converted to a transcript. Other reply modes only keep the attachment file, and the Agent cannot read its content

  • Parsing happens when the Agent replies, so the first reply may be slower when there are many attachments or the files are large. Parsing costs are charged to Credits according to the knowledge base's parser rules.

  • Attachments belong only to that conversation and do not enter the knowledge base. Retention follows the platform's attachment cleanup settings; once expired, the attachments and their parsed copies are deleted automatically. See Credits Billing System.

  • The attachment tools can be turned off individually in the Agent's advanced settings; see Configure Tools for an Agent. For processing details, see Technical Manual - How Message Attachments Are Processed.

Can Email Content Be Exported?

The Email channel has no "export to PDF/Excel" feature, and the Agent does not convert incoming email content into files. Incoming emails and replies both become conversation records, which you can view in All Conversations, or filter in Agent Monitoring and export in batches to Excel (see Conversation Viewer: Batch Export). To turn the content of a single email into a document, ask the Agent to produce it with Canvas and then download it.

Last updated

Was this helpful?