Hello Make Community,
Summary:
The current Make Zoho Creator modules (including the “Make an API Call” advanced module) only support the legacy Zoho Creator API endpoint (creator .zoho. com). Newer Zoho Creator deployments, including all U.S. and most global accounts created in the past year, are now hosted on the creatorapp. zoho . com (spacing is in place on purpose in this post because the Community won’t let me post thinking it is a link) platform. This breaks all native Make Zoho Creator integrations and OAuth token handling for these accounts, at least as I understand things.
Details:
My Zoho Creator app is only accessible via https://creatorapp.zoho.com, not creator.zoho.com.
When I attempt to connect using Make’s Zoho Creator native modules (including “Make an API Call”), all requests are routed to creator .zoho. com, resulting in constant 401 and 404 errors.
I have verified my OAuth credentials, scopes, and account ownership, and I have full admin rights in Zoho Creator.
The standard OAuth flow (via the built-in connector) fails, and the advanced HTTP module only works if I manually manage access tokens and use the correct creatorapp .zoho. com API endpoint.
This manual workaround is unsustainable for business automations, as it requires constant refresh token management.
Attempts & Workarounds:
I am able to authenticate and make API calls using the HTTP module directly against creatorapp .zoho. com, but only by building my own refresh token logic and managing all authentication myself.
The Make’s built-in Zoho Creator OAuth connection and modules are hardcoded to creator .zoho. com and fail for my account.
Zoho’s own support states that the “new” Creator deployments will be on creatorapp .zoho. com moving forward.
My Requests:
-
Please update the Zoho Creator modules in Make to support
creatorapp .zoho. comas an API base URL. This should be selectable or auto-detected during account connection. -
Document this regional/host split in official Make help docs so new Creator users understand why their connections fail.
-
If there are recommended best practices or ETA for support, please share. Manual token management is not scalable for production.
If any users have a supported workaround for full-featured, automated Zoho Creator v2 integration on creatorapp .zoho. com (with automatic token refresh), please share your approach.
Thank you in advance for addressing this critical integration gap. This issue is currently blocking a production-grade business process for us and will affect more Zoho Creator users over time.