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
- A Zoho Cliq account
- Permission to create bots in your Cliq workspace
- A Heffl account
Setup Instructions
Step 1: Create a Zoho Cliq bot
You need a bot in your Zoho Cliq workspace before connecting Heffl.- Open Zoho Cliq
- Go to Bots & Tools → Bots → Add Bot
- Give the bot any name you like (e.g. Heffl Notifications) and choose an icon
- Set Access Level to Personal (just you) or Organization depending on who should be able to use it
- Save the bot
Step 2: Copy the bot’s API endpoint URL
- In Zoho Cliq, open your newly created bot
- Look for the API Endpoint section
-
Copy the URL — it looks like:
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
- In Heffl, go to Settings → Integrations
- Find Zoho Cliq and click Connect
- 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 atcliq.zoho.com, chooseGlobal (.com); ifcliq.zoho.in, chooseIndia (.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.
- Region — pick the Zoho data center your account uses (
- Click Connect
- You’ll be redirected to Zoho’s consent screen — review the permissions and click Accept
- You’ll land back in Heffl with the integration connected
Step 4: Configure which events fire to Cliq
- Go to Settings → Notification Preferences
- 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
- Each event row has three toggles: In-App, Email, and Cliq
- Important events (deal won, invoice paid, lead assigned, mentioned, document signed, etc.) have Cliq enabled by default
- 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 OAuthinvalid_code error. To check, look at the URL when you log into Zoho Cliq:
| Cliq URL | Region |
|---|---|
cliq.zoho.com | Global (.com) |
cliq.zoho.in | India (.in) |
cliq.zoho.eu | Europe (.eu) |
cliq.zoho.com.au | Australia (.com.au) |
cliq.zohocloud.ca | Canada (.ca) |
cliq.zoho.uk | United Kingdom (.uk) |
cliq.zoho.jp | Japan (.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
- A Heffl event fires (e.g., a deal stage changes, an invoice is paid)
- 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
- Cliq sends are fire-and-forget — if Cliq is unreachable, in-app and email delivery are unaffected
- 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:- Go to Settings → Integrations
- Find Zoho Cliq and click Disconnect
Troubleshooting
OAuth fails with `invalid_code` error
OAuth fails with `invalid_code` error
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.Notifications not appearing in Cliq
Notifications not appearing in Cliq
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)
- 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
DM arrives in Cliq but the link inside doesn't open Heffl
DM arrives in Cliq but the link inside doesn't open Heffl
Some Cliq clients render plain URLs as text rather than links. Long-press the URL on mobile to open it, or copy-paste it into a browser.
Refresh failed / `oauthtoken_invalid` errors in server logs
Refresh failed / `oauthtoken_invalid` errors in server logs
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
Does each team member need to set up their own Cliq integration?
Does each team member need to set up their own Cliq integration?
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.
Do I need a separate bot per user?
Do I need a separate bot per user?
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.
Can I send notifications to a Cliq channel instead of a DM?
Can I send notifications to a Cliq channel instead of a DM?
Not currently — the v1 integration only supports personal DMs.
What permissions does Heffl need on Zoho Cliq?
What permissions does Heffl need on Zoho Cliq?
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.Will I still get in-app notifications if Cliq is connected?
Will I still get in-app notifications if Cliq is connected?
Yes. Cliq is an additional delivery channel, not a replacement. In-app, email, and Cliq are independent toggles per event.