Zoho Mail

Connect AI agents to Zoho Mail business mailboxes. Agents send email, search and read full message content, and keep inboxes organized by marking messages read or unread, archiving, flagging spam, and moving them between folders.

8 actions OAuth available

Zoho Mail website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A scheduled sweep runs against the shared inquiries mailbox every fifteen minutes

Search Messages finds unread mail matching the intake patterns: quotes, orders, support requests

Get Message pulls the full body of each match so the agent can classify and extract the details

Routine inquiries get a drafted reply; anything mentioning pricing exceptions or complaints is set aside

The operations lead reviews the set-aside drafts, edits one, approves the rest

Send Email dispatches the approved replies from the business mailbox

Update Messages marks the handled mail read, and Move Messages files it into the processed folder

What This Integration Enables

A business mailbox is the oldest API most companies have: customers, vendors, and leads all write to it, and somebody has to read what they sent. This connector puts an agent on that job. FlowRunner agents search Zoho Mail with scoped expressions like from and subject filters, pull full HTML or plain-text bodies for extraction, send email from any address the account is allowed to use, and keep the mailbox honest by marking, archiving, and moving messages as work completes. The design stance: reading at machine speed is pure upside, and sending in your company's name deserves a checkpoint. The connector supports both, and FlowRunner lets you draw the line between them per workflow. - Send transactional and notification email from a business mailbox inside any flow - Search and read incoming mail to trigger downstream steps and extract structured data - File, flag, archive, and mark messages so mailbox state tracks workflow state - Discover account IDs, from-addresses, and folder structure that other automations depend on The organizing actions matter more than they look. When Update Messages and Move Messages run as the closing step of every triage flow, the mailbox itself becomes an audit trail: unread means untouched, the Processed folder means handled, and anyone can verify the automation's coverage by opening the inbox. That legibility is what makes a shared mailbox automatable without making it opaque.

Without FlowRunner

The shared inbox as a job Someone owns "checking the mailbox," and response time depends on their calendar

Data trapped in message bodies Order details, lead info, and invoice references get retyped from email into other systems

Inbox state means nothing Read, unread, and folder placement reflect who clicked what, not what has actually been handled

With FlowRunner

Mail triages itself Agents search, read, classify, and route incoming messages minutes after they arrive

Extraction is automatic Message content flows into CRMs, sheets, and order systems without retyping

The inbox reflects reality Handled mail is marked, filed, and findable, because folder state is maintained by the workflow

Use Case Scenarios

Order confirmations from the mailbox customers already know

A new order fires in [Shopify](/integrations/shopify). The agent composes the confirmation with the order details and calls Send Email from the orders@ address customers recognize and reply to. Because the mail comes from the real business mailbox rather than a no-reply relay, replies land back in a folder the same agent watches, and a customer question about their order enters the triage flow automatically.

Leads stop dying in the inbox

Inquiry mail arrives at hello@ around the clock. The agent runs Search Messages for unread mail, pulls each full body with Get Message, and extracts the sender, company, and request. Each one becomes a record in [Zoho CRM](/integrations/zoho-crm) with the original message attached, then Move Messages files the email under Processed and Update Messages marks it read. Monday morning starts with a populated pipeline instead of a weekend backlog, and no lead waits three days because its email sat below the fold.

The invoice mailbox that feeds accounting

Vendors send invoices to an ap@ mailbox. On a schedule, the agent searches for messages with invoice-shaped subjects, reads each body, and logs sender, subject, and received time to [Google Sheets](/integrations/google-sheets) for the accounting team's intake queue. Suspected duplicates and unrecognized senders are flagged rather than filed, and a person rules on those before they enter the payable process. The mailbox becomes a structured intake channel instead of a pile.

Human-in-Loop Highlight

Send Email is the operation in this connector that leaves the building. A message dispatched from your company's mailbox reaches a customer or vendor with your domain in the from line, and there is no API call that un-sends it, un-quotes the wrong price, or un-CCs the wrong recipient list. FlowRunner workflows therefore split outbound mail by stakes: template-driven confirmations with machine-verified inputs flow straight through, while anything composed by the agent in free text, anything touching money, and anything responding to a complaint stops in a review queue first. The operations lead reads the draft exactly as the recipient would, and approval is what triggers Send Email. Update Messages deserves the same respect in one narrow case: marking mail as spam trains the mailbox to bury that sender, so spam flagging on ambiguous senders routes through a person too.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Accounts and Folders

List Accounts Lists all mailboxes the connected user can access, with account ID, from-addresses, display name, and settings. The discovery step every other action builds on.
List Folders Lists a mailbox's system and custom folders with ID, name, path, and unread and message counts. Folder IDs feed listing, fetching, and filing.

Reading Mail

List Messages Lists messages in an account, optionally scoped to a folder and filtered by read or flag status. Returns summaries with subject, sender, received time, and the IDs needed to fetch full content. Paginated.
Search Messages Searches an account using Zoho's search syntax: plain text against subject, sender, and body, or scoped expressions like from and subject filters. The precision tool behind intake workflows.
Get Message Retrieves one message's full content, including the HTML or plain-text body and metadata. The extraction step that turns an email into structured data.

Sending Mail

Send Email Sends an email from an allowed from-address, with To, CC, and BCC recipients, a subject, and an HTML or plain-text body. The action this page's human gate governs.

Organizing Mail

Update Messages Updates the status of one or more messages in a single call: read or unread, flagged, archived, or marked as spam. The bookkeeping that keeps mailbox state matching workflow state.
Move Messages Moves one or more messages to a different folder in the same account. The filing step at the end of every triage flow.

Frequently Asked Questions

What can FlowRunner do with Zoho Mail?

FlowRunner agents can run List Accounts, List Folders, and List Messages in Zoho Mail, plus 5 more actions.

Does connecting Zoho Mail to FlowRunner require OAuth?

Yes. Zoho Mail connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Zoho Mail trigger a FlowRunner workflow automatically?

Zoho Mail doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Zoho Mail

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us