> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/integrations/communications/imap-email.md). # IMAP Email With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from IMAP Email and, when **Write** access is enabled, perform approved actions in IMAP Email. The IMAP Email integration connects any IMAP and SMTP compatible mailbox to Filed using server credentials you provide. It is the most flexible email option and works with custom business email addresses, hosted Exchange servers, and any other provider that supports standard IMAP access. ## What this integration does IMAP Email authenticates directly with your mail server using a username and password (or an app-specific password if your provider requires one for third-party clients). Filed establishes an IMAP connection to read your mailbox and an SMTP connection to send messages. Because this integration works at the protocol level rather than through a provider-specific API, it is compatible with a wide range of mail servers. However, since IMAP credentials cannot be refreshed automatically the way OAuth tokens can, the connection will show an error if your password changes and will need to be reconnected with updated credentials. SMTP does not automatically copy sent messages to a Sent folder on the server. Whether a copy appears in your Sent folder depends on your mail server's configuration and any rules you have set in your email client. ## Before you start You need the following information from your email provider or IT administrator: * IMAP server hostname and port (typically port 993 with TLS) * SMTP server hostname and port (typically port 587 with TLS) * Your email username (usually your full email address) and password * Whether each server requires TLS If your provider requires an app-specific password for IMAP access (common with accounts that have two-factor authentication enabled), generate that password before starting. Do not use your main account password if the provider does not support it for IMAP. Common server settings for reference: | Provider | IMAP Host | IMAP Port | SMTP Host | SMTP Port | | ---------------- | --------------------- | --------- | ------------------ | --------- | | Google Workspace | imap.gmail.com | 993 | smtp.gmail.com | 587 | | Microsoft 365 | outlook.office365.com | 993 | smtp.office365.com | 587 | | Apple iCloud | imap.mail.me.com | 993 | smtp.mail.me.com | 587 | For Google Workspace accounts, use the dedicated Gmail integration instead of IMAP Email if possible, as it handles the App Password flow with pre-filled server settings. ## Connecting IMAP email to Filed Filed prompts for your IMAP server host, port, username, and password. SMTP settings default to the same host as your IMAP server; expand Advanced settings to enter a different SMTP host, port, or separate SMTP credentials if your provider uses different servers for inbound and outbound mail. ## What Filed can do with IMAP email **List mailboxes** - returns all folders present on the IMAP server for the connected account, including any server-side folder hierarchy your provider maintains. **List messages** - retrieves an envelope listing of messages in any mailbox folder, with support for a keyword search query, a date filter (messages received after a given date), a maximum result count, and pagination using a continuation token. **Get message** - fetches the full content of a specific message identified by its mailbox path and UID. The response includes the subject, sender, recipients (To and CC), date, plain-text and HTML body, read/unread status, and a list of attachments with each attachment's filename, content type, and size. **Send message** - composes and sends a message from the connected account via your SMTP server. Supports To, CC, and BCC recipients, a subject, and a plain-text or HTML body. ## Troubleshooting **Authentication failed** - The IMAP server rejected the username or password. Verify that you are using the correct credentials for IMAP access. If your provider requires an app-specific password for third-party clients (rather than your main account password), generate one and use that instead. **Connection refused or timeout** - Filed cannot reach the IMAP server at the address and port entered. Double-check that the hostname and port are correct. Some providers require you to enable IMAP access in your account settings before a third-party client can connect; consult your provider's documentation. **SMTP sending fails but IMAP reads correctly** - The SMTP settings may differ from the IMAP settings. Expand Advanced settings in the connection form and confirm the SMTP host and port are correct. If your provider uses separate credentials for outbound mail, enter them in the SMTP username and password fields. **Connection worked previously but now shows an error** - If your password changed, the stored credentials are no longer valid. Reconnect the integration with the updated password. Some servers also close idle connections after extended inactivity; if errors appear intermittently, confirm with your provider that persistent third-party connections are supported. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding IMAP Email information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with IMAP Email data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find recent IMAP Email information related to \[client name] and summarize the key items.” * “Show me anything from the last 30 days that needs a response or follow-up.” * “With write access enabled, create the approved follow-up for \[client name] for my review.” ## Capabilities ### Review communication context Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests. ### Coordinate approved follow-up When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach. ### Keep access scoped to the right account The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/reference/plugins/integrations/communications/imap-email.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.