Zoho Cliq

Send messages from AI agents into Zoho Cliq channels, group chats, and direct conversations, with rich cards, buttons, and attachments. Agents also create and manage channels and look up users and contacts to route notifications to the right destination.

10 actions OAuth available

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

An exception fires in another system, an order fails validation during fulfillment processing

List Users resolves the on-call operations owner by email

Send Direct Message delivers a rich card to that owner with the order detail and two buttons: approve or hold

The agent waits on the response, escalating if the card sits unanswered past the SLA window

The owner reads the context and taps a decision without leaving Cliq

The originating flow resumes on the chosen branch and completes the order handling

Send Channel Message posts the outcome to the team channel so the decision is on the record

What This Integration Enables

For teams running on Zoho, Cliq is where work gets discussed, which makes it where automated work should surface. This connector treats Cliq as more than a notification sink: with rich cards, interactive buttons, and attachments on every message action, it turns chat into the decision surface for FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration. An agent can pause mid-flow, deliver full context to exactly the right person, and resume the moment they answer, all inside the tool the team already has open. - Post event alerts from any system into the right channel: orders, deals, tickets, deploys - Deliver direct messages with cards and buttons that carry a decision, not just a link - Post updates into existing one-to-one and group chats by chat ID - Spin up channels on demand and seed them with the right members for a project or incident - Resolve users, contacts, chats, and channels so every message routes to the correct destination The difference between an alerting bot and an orchestration layer is what happens after the message sends. FlowRunner waits for the answer. That waiting is a difference in kind, not degree. A webhook that posts a card and moves on has notified someone; an agent that posts the card, holds the flow, and resumes on the answer has delegated a decision. Cliq's buttons and cards give the decision a clean surface, and FlowRunner gives it a place in the flow's logic, with the timeout, the escalation path, and the audit record all defined before the first card ever sends.

Without FlowRunner

Alerts scattered across inboxes Exceptions land in email, get filtered, and get found the next morning

Notifications without next steps A message says something broke, and acting on it means opening three other systems

Channel noise nobody trusts Every automation posts everything everywhere, so people mute the channel that mattered

With FlowRunner

Decisions arrive where the team lives Agents deliver context and action buttons directly into Cliq, to the person who owns the call

The message is the workflow Approve or hold happens in the card, and the flow resumes the moment a human answers

Signal calibrated by design Routine outcomes post quietly to team channels; only genuine decisions interrupt a person

Use Case Scenarios

The fulfillment channel that reads itself

When a new order fires from [Shopify](/integrations/shopify), the agent calls Send Channel Message to post a rich card into the fulfillment channel: items, destination, and shipping tier, with the order link one tap away. High-value orders add an approve button that gates the fulfillment handoff. The channel becomes a live order feed the team can act from, not a log they scroll past.

The deal alert that finds its owner

When a new deal lands in [Zoho CRM](/integrations/zoho-crm), the agent calls List Users to resolve the assigned rep's email, then Send Direct Message with a card carrying the deal size, source, and next step. No shared channel spam, no missed handoffs: the one person who owns the deal gets the one message that matters, and the agent logs delivery for pipeline hygiene.

An incident channel in the time it takes to read the ticket

A priority ticket in [Zoho Desk](/integrations/zoho-desk) trips the incident flow. The agent calls Create Channel with a named channel for the incident, seeds it with the responders' emails, and posts the ticket detail as the first message. As the flow gathers diagnostics from other systems, Send Chat Message appends findings to the running conversation. When the incident closes, the channel holds the whole timeline, built while the humans worked the problem.

Human-in-Loop Highlight

The costly operation in a chat connector is not deleting anything. It is Send Channel Message aimed at an organization-level channel. Cliq channels carry a level, organization, team, private, or external, and a message to an organization channel interrupts everyone in the company at once. Automations that blast org-wide channels burn the team's trust in every future alert, which quietly kills the approval workflows that depend on people actually reading the cards. So FlowRunner agents hold a rule: posts to team channels and direct messages flow freely, but any message bound for an organization-level channel pauses for a person to approve the copy and confirm the audience. Get Channel makes the check trivial: the level field is right there. One approval protects the attention budget every other workflow spends.

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

10 actions

Messaging

Send Channel Message Posts to a channel by its unique name, with plain text plus a rich card, interactive buttons, and file attachments. The workhorse for team-facing alerts and approvals.
Send Direct Message Sends a direct message to a user by email or ZUID, with the same card, button, and attachment support. The delivery step for personal approvals and reminders.
Send Chat Message Posts into an existing one-to-one or group conversation by chat ID. Used to append updates to a running discussion.

Channels

List Channels Retrieves a paginated list of accessible channels, optionally restricted to joined channels. The lookup behind routing decisions.
Get Channel Retrieves a channel's title, description, level, participant count, and the connected user's role. The check that tells an agent how wide an audience a post will reach.
Create Channel Creates a channel with a name, optional description, level, and initial member emails. The step that spins up incident and project spaces on demand.

Chats, Users, and Contacts

List Chats Retrieves the connected account's conversations with chat IDs, titles, and types. The reference read for Send Chat Message.
List Users Retrieves organization users with name, email, and ZUID. The resolution step before any direct message.
Get User Retrieves a single user's full profile by ZUID, including status and role. Pass "me" to identify the connected account.
List Contacts Retrieves the account's contacts with name, email, ZUID, and presence. Used to find people available for a direct conversation.

Frequently Asked Questions

What can FlowRunner do with Zoho Cliq?

FlowRunner agents can run Send Channel Message, Send Direct Message, and Send Chat Message in Zoho Cliq, plus 7 more actions.

Does connecting Zoho Cliq to FlowRunner require OAuth?

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

Can Zoho Cliq trigger a FlowRunner workflow automatically?

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

Start building with Zoho Cliq

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

Start Building Free Talk to us