--- title: "Zoho SalesIQ Integration" description: "Read Zoho SalesIQ live chat activity from AI agents. Agents pull conversations filtered by status, department, or operator, fetch full transcripts, track website visitors by portal view, and look up operators and departments for routing and reporting." url: https://flowrunner.ai/integrations/zoho-salesiq date_modified: 2026-08-01T02:40:32-07:00 --- # Zoho SalesIQ [Communication](https://flowrunner.ai/integrations/category/communication-messaging) Read Zoho SalesIQ live chat activity from AI agents. Agents pull conversations filtered by status, department, or operator, fetch full transcripts, track website visitors by portal view, and look up operators and departments for routing and reporting. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · OAuth · available [Zoho SalesIQ website](https://zoho.com/) · [Platform Documentation](https://www.zoho.com/salesiq/help/developer-section/) · Capability data verified 2026-07-28 1. A scheduled sweep runs every 15 minutes during business hours 2. List Conversations pulls chats with status missed in the last window, scoped by department 3. Get Conversation fetches each missed chat's visitor details and any partial transcript 4. Agent matches the visitor against the CRM to see if this is a known account or an anonymous browser 5. A support lead reviews the drafted follow-up for known accounts before anything reaches the visitor, because an apology sent to the wrong contact on a live deal does damage a dashboard never shows 6. Approved follow-ups go out, and the missed-chat alert posts to the support channel with operator availability attached 7. List Operators runs so the alert names who was online when the chat was missed ## What This Integration Enables Live chat produces some of the most honest data a company has: what visitors actually asked, in their own words, and whether anyone answered. Zoho SalesIQ keeps that data, and this connector is built on a clear-eyed view of what to do with it: read it out, systematically, into the places where decisions get made. FlowRunner agents list conversations filtered by status, department, operator, and time window, pull full transcripts, walk tracked visitors by portal view, and resolve operators and departments for routing and attribution. This is a read connector by design. It does not send chats or message visitors, which makes it the safe half of a follow-up flow: SalesIQ supplies the evidence, and the customer-facing move happens in your CRM, helpdesk, or email system with FlowRunner's oversight applied there. That separation is a feature, not a gap: the system holding the raw customer voice should not also be the system improvising replies to it. - Sweep for missed and unresolved chats on a schedule instead of at month end - Land transcripts in the CRM or helpdesk record where the account team will read them - Sync visitor segments into lead pipelines - Attribute chat volume to real operators and departments for staffing decisions ### Without FlowRunner **Chat data dies in the widget**: Transcripts, missed chats, and visitor sessions live in the SalesIQ portal and never reach the systems where follow-up happens **Missed chats surface at month end**: Someone discovers the missed-chat count in a report weeks after the visitors moved on **Reporting is a manual export**: Chat volume by department and operator gets assembled by hand, when anyone has time ### With FlowRunner **Conversations feed the pipeline**: Transcripts and visitor records flow into the CRM, the helpdesk, and the dashboard the day they happen **Missed means minutes, not weeks**: A recurring sweep surfaces missed chats while the visitor still remembers asking **Reporting runs itself**: Agents page through conversations on schedule and the numbers land where the team already looks ## Use Case Scenarios ### The missed-chat sweep Every 15 minutes, List Conversations runs with status missed against the sales department's ID from List Departments. Each hit gets Get Conversation for the visitor identity and whatever the visitor managed to type. Known accounts route to the owning rep with a drafted follow-up held for approval; anonymous visitors post to [Slack](https://flowrunner.ai/integrations/slack) with the page they were on. The gap between "a prospect asked a question" and "someone knows" drops from a monthly report to a coffee break. ### Transcripts that reach the ticket When a chat closes without resolution, the agent pulls the full transcript with Get Conversation and opens a ticket in [Zoho Desk](https://flowrunner.ai/integrations/zoho-desk) carrying the visitor, department, attending operator, and the conversation text. The support engineer who picks it up reads what was already said instead of asking the customer to repeat it. Closed-and-resolved chats skip the ticket and log a summary row to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the weekly quality review. ### Returning visitors become named leads List Visitor Views resolves the "Returning Visitors" segment, and a nightly run of List Visitors pages through it. Visitors with an identified email get upserted into [HubSpot](https://flowrunner.ai/integrations/hubspot) as leads with their visit history noted; the rest accumulate in a watch list. When a returning visitor later starts a chat, the conversation record and the CRM record finally describe the same person, and the rep opens the call knowing it is the fourth visit, not the first. ## Human-in-Loop Highlight The costly operation in a SalesIQ flow is not the API call, it is what the flow does with a transcript. Get Conversation hands an agent a verbatim record of a customer being frustrated, confused, or about to churn, and the tempting automation is to fire a follow-up the moment a missed or unresolved chat appears. FlowRunner flows put a person between the transcript and the outreach: the agent assembles the evidence, missed chat at 2:14pm, visitor matched to an account with an open renewal, operator shown as available by List Operators at the time, and a support lead decides whether the right move is an apology, a call from the account manager, or silence. Reading the room is the judgment call; the connector's job is making sure the room is fully read. The lead answers in one click, and the decision, with its evidence, is on the flow's record for the next quality review. 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 6 actions ### Conversations 2 - **List Conversations** Retrieves a paginated list of chats filtered by status (open, closed, missed, and more), department, attending operator, and a time window in epoch milliseconds, with cursor paging for large lists. The backbone of sweeps and reporting. - **Get Conversation** Retrieves a single chat by conversation ID: visitor, department, attending operator, status, timestamps, and the message transcript when available. The action that turns a chat ID into evidence. ### Visitors 2 - **List Visitors** Retrieves tracked website visitors, optionally scoped to a named visitor view, with cursor paging. The feed behind lead sync and returning-visitor plays. - **List Visitor Views** Retrieves the visitor views configured in the portal, such as "Today's Visitors" or "Returning Visitors", including custom views. Supplies the view IDs that scope List Visitors to a segment. ### Operators 1 - **List Operators** Retrieves the portal's operators with ID, name, email, role, and availability status. Used to attribute conversations, check who was online, and resolve IDs for filtering. ### Departments 1 - **List Departments** Retrieves the portal's departments with IDs and names. Departments group operators and route chats; the IDs scope conversation sweeps to the team that owns them. ## Frequently Asked Questions ### What can FlowRunner do with Zoho SalesIQ? FlowRunner agents can run List Conversations, Get Conversation, and List Visitors in Zoho SalesIQ, plus 3 more actions. ### Does connecting Zoho SalesIQ to FlowRunner require OAuth? Yes. Zoho SalesIQ connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Zoho SalesIQ trigger a FlowRunner workflow automatically? Zoho SalesIQ doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Zoho SalesIQ?** This integration exposes Zoho SalesIQ 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-salesiq. Site index: https://flowrunner.ai/llms.txt