PipedreamHQ / PipedreamHQ/pipedream

Zoho Cliq

Open
#21,439 0 comments 0 reactions 0 assignees View on GitHub
Backlog - For Review bug triaged user request
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

### App
Zoho Cliq

### Summary:
Connecting a Zoho Cliq account on a non-US data center (e.g. India / zoho.in) always fails: the connection TEST request is hardcoded to cliq.zoho.com and returns 401, so the account is never saved.

### Details:
Repro:
1. Connect a Zoho Cliq account whose data center is India (zoho.in).
2. In the connect screen, set Region = "India (zoho.in)" (the base_api_url custom field).
3. Authorize — the OAuth correctly goes to accounts.zoho.in and succeeds.
4. The connection then immediately fails.

Error (from the Connect CONNECTION_ERROR webhook):
"401 error when making test request to cliq.zoho.com/api/v2/channels"
request_type: "test", status_code: 401, url: https://cliq.zoho.com/api/v2/channels

Impact:
Every non-US Zoho Cliq account (zoho.in, zoho.eu, zoho.com.au, zoho.jp, zohocloud.ca, zoho.sa, zoho.uk) fails the connection test. Because the test fails, the account is discarded and never persisted, so Zoho Cliq is completely unusable for
these data centers — even though the actions themselves are already region-aware.

### Screenshots:

![Screenshot](https://storage.tally.so/private/Screenshot-2026-07-22-at-12.44.56-PM.png?id=6yMD1o&accessToken=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjZ5TUQxbyIsImZvcm1JZCI6Im5yampSdiIsImlhdCI6MTc4NDcwNjIwN30.qyNXK8TYlIoE1OOyXTsNwS39gfTBoWDGJPA2ZVbfReI&signature=00e4caca28cb1c37747a97e1ea93d0d007081190b387c87333813be1f94bed18)

Contributor guide

Open the contributing guide

Research direction

Start at the Zoho Cliq connection flow and the CONNECTION_ERROR test request, tracing how the base_api_url custom field is used after OAuth authorization. Verify that the connection test targets the selected data center rather than cliq.zoho.com, and confirm that an India-region account can complete the test and be persisted.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.