Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.heffl.com/llms.txt

Use this file to discover all available pages before exploring further.

Zoho Cliq Integration

Connect Zoho Cliq to Heffl to receive notifications as direct messages from a bot in your Cliq account — alongside in-app and email notifications.

Overview

When connected, Heffl sends each enabled notification (deal won, invoice paid, lead assigned, mentioned in a comment, etc.) as a DM in your personal chat with a Zoho Cliq bot. Notifications are personal — each user connects their own Cliq account, and the bot only DMs that user.

Prerequisites

  1. A Zoho Cliq account
  2. Permission to create bots in your Cliq workspace
  3. A Heffl account

Setup Instructions

Step 1: Create a Zoho Cliq bot

You need a bot in your Zoho Cliq workspace before connecting Heffl.
  1. Open Zoho Cliq
  2. Go to Bots & Tools → Bots → Add Bot
  3. Give the bot any name you like (e.g. Heffl Notifications) and choose an icon
  4. Set Access Level to Personal (just you) or Organization depending on who should be able to use it
  5. Save the bot

Step 2: Copy the bot’s API endpoint URL

  1. In Zoho Cliq, open your newly created bot
  2. Look for the API Endpoint section
  3. Copy the URL — it looks like:
    https://cliq.zoho.com/api/v2/bots/{bot_unique_name}/message
    
Cliq strips hyphens and special characters from the bot’s display name when generating the unique name. For example, a bot named “heffl-notifications” becomes hefflnotifications in the URL. Always use the URL value, not the display name.

Step 3: Connect Zoho Cliq in Heffl

  1. In Heffl, go to Settings → Integrations
  2. Find Zoho Cliq and click Connect
  3. Fill in the form:
    • Region — pick the Zoho data center your account uses (Global (.com), India (.in), Europe (.eu), etc.). This must match your Zoho Cliq URL — for example, if you log in at cliq.zoho.com, choose Global (.com); if cliq.zoho.in, choose India (.in).
    • Bot Unique Name — paste either the API endpoint URL you copied in Step 2, or just the unique name (the segment after /bots/). Heffl automatically extracts the unique name from the full URL.
  4. Click Connect
  5. You’ll be redirected to Zoho’s consent screen — review the permissions and click Accept
  6. You’ll land back in Heffl with the integration connected
Heffl automatically enables the Zoho Cliq notifications master toggle on your notification preferences when the integration is connected.

Step 4: Configure which events fire to Cliq

  1. Go to Settings → Notification Preferences
  2. The Zoho Cliq notifications card at the top is the master switch — leave it on to receive Cliq DMs, turn it off to mute all Cliq messages without disconnecting
  3. Each event row has three toggles: In-App, Email, and Cliq
  4. Important events (deal won, invoice paid, lead assigned, mentioned, document signed, etc.) have Cliq enabled by default
  5. Noisy events (status changes, comments, automation notifications, etc.) have Cliq disabled by default — turn them on per event if you want them

Configuration Options

Region

The Zoho data center your account is on. Selecting the wrong region causes the OAuth invalid_code error. To check, look at the URL when you log into Zoho Cliq:
Cliq URLRegion
cliq.zoho.comGlobal (.com)
cliq.zoho.inIndia (.in)
cliq.zoho.euEurope (.eu)
cliq.zoho.com.auAustralia (.com.au)
cliq.zohocloud.caCanada (.ca)
cliq.zoho.ukUnited Kingdom (.uk)
cliq.zoho.jpJapan (.jp)

Bot Unique Name

The identifier of your bot in Zoho Cliq. Either paste the full API endpoint URL (https://cliq.zoho.com/api/v2/bots/{name}/message) or just the unique name. Heffl normalizes either input.

How It Works

  1. A Heffl event fires (e.g., a deal stage changes, an invoice is paid)
  2. Heffl checks each recipient’s notification preferences:
    • In-app notification is sent (controlled by the In-App toggle)
    • Email is queued if Email is on
    • Cliq DM is sent if both the Zoho Cliq notifications master switch AND the per-event Cliq toggle are on, and the user has a connected Cliq integration
  3. Cliq sends are fire-and-forget — if Cliq is unreachable, in-app and email delivery are unaffected
  4. Heffl uses the connecting user’s OAuth token to post a message via your bot. The bot DMs you in your personal chat with it.

Disconnecting

To disconnect Zoho Cliq:
  1. Go to Settings → Integrations
  2. Find Zoho Cliq and click Disconnect
This revokes Heffl’s access to your Cliq account. The bot remains in your Cliq workspace — you can re-use it on reconnect or delete it manually in Cliq. To temporarily mute Cliq notifications without disconnecting, turn off the Zoho Cliq notifications master toggle in your notification preferences instead.

Troubleshooting

Cause: the Region you selected during connect doesn’t match the Zoho data center where your account lives. Auth codes are region-bound — generated by .com and redeemed at .in will fail.Fix: disconnect, reconnect, and pick the region that matches your Zoho Cliq URL.
Possible causes:
  • The Zoho Cliq notifications master toggle is off
  • The per-event Cliq toggle for that specific event type is off
  • The integration is disconnected
  • The bot unique name is wrong (Cliq returns 404 on send)
Solutions:
  • Verify the master toggle and per-event Cliq toggle are on in Settings → Notification Preferences
  • Confirm the integration shows as Connected in Settings → Integrations
  • Open your bot in Zoho Cliq, copy the API endpoint URL, and paste it back into the integration’s Bot Unique Name field — this guarantees the value matches Cliq’s actual unique name
Cause: the integration’s OAuth token can’t be refreshed — usually because the refresh token was revoked from Zoho’s side, or the bot was deleted from Cliq.Fix: disconnect the integration in Heffl and reconnect.

FAQ

Yes. Cliq DMs are personal — each user connects their own Zoho Cliq account so the bot can DM them individually. The bot itself can be shared (one bot in your Cliq workspace, used by everyone), but each Heffl user must do their own OAuth connect.
No. One bot in your Cliq workspace can serve all users. Each user pastes the same bot unique name during their own connect, and Heffl uses each user’s individual OAuth token to send DMs to that user.
Not currently — the v1 integration only supports personal DMs.
Heffl requests the ZohoCliq.Webhooks.CREATE scope, which lets it post messages to your bot. It cannot read messages, channels, or any other content in your Cliq account.
Yes. Cliq is an additional delivery channel, not a replacement. In-app, email, and Cliq are independent toggles per event.