--- title: "Zoho TeamInbox Integration" description: "Zoho TeamInbox is Zoho's shared inbox for teams. Agents list and search conversations, assign, archive, snooze and close threads, send email from a team address, and create contacts across your organization's inboxes." url: https://flowrunner.ai/integrations/zoho-teaminbox date_modified: 2026-09-04T19:38:13-07:00 --- # Zoho TeamInbox [Communication](https://flowrunner.ai/integrations/category/communication-messaging) Zoho TeamInbox is Zoho's shared inbox for teams. Agents list and search conversations, assign, archive, snooze and close threads, send email from a team address, and create contacts across your organization's inboxes. 13 actions · OAuth · available [Zoho TeamInbox website](https://www.zoho.com/teaminbox/) · [Platform Documentation](https://www.zoho.com/teaminbox/) · Capability data verified 2026-08-19 1. A scheduled poll reads the shared inbox for conversations that arrived since the last run 2. List Inbox Threads returns each conversation's subject, sender, summary and read state 3. List Inboxes reads the auto assign and auto archive settings before the flow acts on them 4. Agent classifies each thread and matches the sender against the CRM record 5. Assign Thread routes it to the right member by member id, and Follow Thread keeps the flow watching 6. Anything urgent posts to the team channel with the summary and the assignee 7. A person writes the reply, and decides whether answering it also closes it ## What This Integration Enables A shared inbox is different from a helpdesk in one way that matters for automation: the agent is not filing tickets, it is acting inside the address a customer already writes to. Zoho TeamInbox models that as organizations, teams, inboxes and conversations, and FlowRunner agents work down that chain because everything hangs off it. They list and search conversations across an organization, assign threads to a specific member by member id rather than by email address, archive, trash and follow threads, send from an address the inbox is actually permitted to send from, and create contacts that carry social profiles alongside an email and a phone number. The most useful read here is not a conversation. It is List Inboxes, because the inbox settings say whether the platform is already doing what a workflow is about to do: auto assign, auto add, and unassign on archive. Building a routing agent on top of an inbox that already auto assigns produces two owners and no clarity. Reading the settings first is the difference between [connectors](https://flowrunner.ai/concepts/connectors) that cooperate with a platform and automation that fights it. ### Without FlowRunner **Triage by whoever looks first**: A shared address is worked from the top down, so the oldest thread waits longest **Ownership unclear**: Two people reply to the same conversation because neither knew it was claimed **Closed too early**: A thread is archived along with the reply, and the follow-up arrives with no owner ### With FlowRunner **Triage on a schedule**: Conversations are read, classified and assigned continuously rather than in bursts **Ownership recorded**: Each thread carries an assignee before anybody starts typing **Closing is a separate decision**: Answering and closing are treated as two calls, because they are two judgments ## Use Case Scenarios ### Routing a shared address without two people answering the same thread The agent polls List Inbox Threads for the support address, classifies each new conversation, and matches the sender against the record in [Zoho CRM](https://flowrunner.ai/integrations/zoho-crm) or [HubSpot](https://flowrunner.ai/integrations/hubspot). It resolves the right owner with List Team Members and calls Assign Thread with that person's member id, which is what the API takes rather than an email address. Follow Thread keeps the flow notified of everything that happens on the conversation afterward, whether or not it is assigned to the connected account. The customer sees one reply, from one person, faster. ### Finding the message a customer swears they sent A customer says they wrote in last week and heard nothing. Search Threads runs across the organization by subject and free text, and the agent explicitly asks for trashed and spam conversations, because they are excluded by default and that exclusion is exactly why a message a customer can see is invisible to the team. When the thread turns up in the trash, the agent reports where it was found rather than quietly restoring it, and posts the finding to [Slack](https://flowrunner.ai/integrations/slack) so the inbox owner can see how it got there. ### Turning an unknown sender into a record An inbound conversation arrives from an address nobody recognizes. The agent creates the person with Create Contact, which carries social profile URLs alongside the email address and mobile number, so the shared inbox holds the same identity the rest of the stack does. It then assigns the thread and opens the corresponding record downstream in [Pipedrive](https://flowrunner.ai/integrations/pipedrive). The reply itself is not written by the agent, because Send Email goes out from the team's own address and the customer will read it as the company speaking. ## Human-in-Loop Highlight Send Email carries an archive flag, and that flag is where this connector's gate lives. Turning it on sends the reply and archives the conversation in the same call, which is exactly right for a notification nobody needs to respond to and exactly wrong for an answer that might not land. If the inbox has unassign on archive switched on, archiving also strips the assignee, so a follow-up from the customer arrives on a thread that has left the active view and belongs to nobody. The reply was fine. The close was the mistake, and it is a mistake nothing in the API reports. So the agent treats answering and closing as two decisions rather than one. It drafts, it assigns, it attaches the CRM context, and it asks the person handling the conversation: "This reply answers the refund question. Sending with archive on closes the thread, and this inbox unassigns on archive, so a follow-up would arrive unowned. Send and close, or send and leave it open?" The same care covers Trash Thread, because a trashed conversation disappears from every read in this connector unless a search explicitly asks for it, which means a workflow that trashes a thread and then cannot find it has not lost it, but the person looking for it has. 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 13 actions ### Organization and Teams 3 - **List Organizations** Lists the organizations the connected account belongs to, each with its unique id and whether it is the default. Everything else in this connector hangs off an organization id, so this is the first call. - **List Teams** Lists the teams inside an organization with their type and member count. A team owns the inboxes, so a team id is needed before any inbox operation. - **List Team Members** Lists the people in a team with their name, email address, role and member id. The member id is what Assign Thread takes as its assignee, rather than an email address. ### Inboxes 2 - **List Inboxes** Lists a team's inboxes with their settings and members. The auto assign, auto add and unassign on archive settings are the ones worth reading, because they decide whether the platform is already doing what a workflow is about to do. - **List Sender Addresses** Lists the addresses an inbox is allowed to send from. Send Email refuses a from address that is not on this list, so it is read first. ### Conversations 3 - **List Inbox Threads** Reads a page of an inbox's conversations with each one's subject, sender, summary, read and archived state and message count. - **Search Threads** Searches an organization's conversations by free text, by subject, or both, optionally narrowed to particular inboxes. Trashed and spam conversations are excluded unless asked for, which is why a message a customer can see may look missing. - **Send Email** Sends a new email from a shared inbox and returns the message and thread ids. The from address must be one the inbox permits, and the archive option sends and archives in one step, which is the decision this page's human gate covers. ### Thread Actions 4 - **Assign Thread** Assigns a conversation to a team member so it shows up as theirs, using a member id rather than an email address. - **Archive Thread** Moves a conversation into the archive, which is how a finished conversation leaves the active inbox without being deleted. On an inbox that unassigns on archive, it also removes the assignee. - **Trash Thread** Moves a conversation to the trash, marking it for deletion. Trashed conversations disappear from every read here unless a search asks for them. - **Follow Thread** Follows a conversation so the connected account is notified about everything that happens on it, whether or not it is assigned to them. ### Contacts 1 - **Create Contact** Creates a contact inside a team and returns its id. A contact records who the team is talking to across channels, which is why it carries social profile URLs alongside an email address and a mobile number. ## Frequently Asked Questions ### What can FlowRunner do with Zoho TeamInbox? FlowRunner agents can run List Organizations, List Teams, and List Team Members in Zoho TeamInbox, plus 10 more actions. ### Does connecting Zoho TeamInbox to FlowRunner require OAuth? Yes. Zoho TeamInbox connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Zoho TeamInbox trigger a FlowRunner workflow automatically? Zoho TeamInbox doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Zoho TeamInbox?** This integration exposes Zoho TeamInbox to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/zoho-teaminbox. Site index: https://flowrunner.ai/llms.txt