# Zoho Bigin setup for PopMCP You paste the Client ID and Client secret of a Server-based Application you register in the Zoho API Console, then sign in with Zoho and choose the Bigin organization to connect. - Auth: OAuth authorization - Setup time: 6 min - API base URL: https://www.zohoapis.com/bigin/v2 - Credentials screen: https://api-console.zoho.com/ - Provider docs: https://www.bigin.com/developer/docs/apis/v2/oauth-overview.html ## Before you begin - A Bigin organization on any edition, the free one included. - A Bigin user whose role and profile can see what the AI should work with. An administrator reaches everything. - Knowing which Zoho data center your account lives in: the domain you sign in at, such as zoho.com, zoho.eu, zoho.in or zoho.com.au. - PopMCP's callback URL from the connect form: https://app.popmcp.com/api/providers/zoho-bigin/callback ## Get your credentials ### 1. Open the API Console for your data center Sign in at api-console.zoho.com as the Zoho user whose Bigin access the AI should have. If your Zoho account lives in another data center, use that data center's console instead, for example api-console.zoho.eu, api-console.zoho.in or api-console.zoho.com.au. Click Get Started on your first visit, or Add Client if you already have clients. Screen: https://api-console.zoho.com/ ### 2. Choose Server-based Applications Pick Server-based Applications and click Create Now. PopMCP signs you in through a redirect, so the other client types, Self Client included, cannot complete the connection. Screen: https://api-console.zoho.com/ ### 3. Name the client and add PopMCP's redirect URI Enter a Client Name such as `PopMCP` and any Homepage URL, for example `https://app.popmcp.com`. Paste `https://app.popmcp.com/api/providers/zoho-bigin/callback` into Authorized Redirect URI, then click Create. Screen: https://api-console.zoho.com/ ### 4. Copy the Client ID and Client Secret Open the Client Secret tab and copy Client ID (it starts with `1000.`) and Client Secret. You only need the Settings tab if people in other data centers will sign in through this client: there you can turn on Multi-DC and tick their data centers. Screen: https://api-console.zoho.com/ ### 5. Paste both values into PopMCP and sign in In PopMCP, paste the values into Client ID and Client secret. Only if you created the client outside zoho.com, open More options and type that data center into Zoho data center, for example `EU`, `IN` or `AU`. Click Sign in with Zoho and accept the permissions. If you belong to several Bigin organizations, choose the one you want on Zoho's consent screen, because this connection reaches only that one. ## Fields PopMCP asks for - Client ID (clientId) [required]: The "Client ID" on your app's Client Secret tab. - Client secret (clientSecret) [required]: The "Client Secret" on the same tab. Stored encrypted and used only on the server. - Zoho data center (dataCenter): Only when your app was made outside zoho.com: the data center its console is in, such as EU (zoho.eu), IN, AU, JP, CA, SA or CN. One of: US, EU, IN, AU, JP, CA, SA, UK, AE, SG, CN. ## Callback URL to register https://app.popmcp.com/api/providers/zoho-bigin/callback ## Scopes requested - ZohoBigin.modules.contacts.READ - ZohoBigin.modules.accounts.READ - ZohoBigin.modules.products.READ - ZohoBigin.modules.pipelines.READ - ZohoBigin.modules.tasks.READ - ZohoBigin.modules.events.READ - ZohoBigin.modules.calls.READ - ZohoBigin.modules.notes.READ - ZohoBigin.modules.attachments.READ - ZohoBigin.settings.modules.READ - ZohoBigin.settings.fields.READ - ZohoBigin.settings.layouts.READ - ZohoBigin.settings.related_lists.READ - ZohoBigin.settings.custom_views.READ - ZohoBigin.settings.tags.READ - ZohoBigin.settings.roles.READ - ZohoBigin.settings.profiles.READ - ZohoBigin.settings.emails.READ - ZohoBigin.users.READ - ZohoBigin.org.READ - ZohoBigin.coql.READ - ZohoBigin.bulk.READ - ZohoBigin.notifications.READ - ZohoBigin.Files.READ - ZohoSearch.securesearch.READ - ZohoBigin.modules.ALL - ZohoBigin.modules.contacts.ALL - ZohoBigin.modules.pipelines.ALL - ZohoBigin.modules.notes.ALL - ZohoBigin.modules.attachments.ALL - ZohoBigin.settings.ALL - ZohoBigin.users.ALL - ZohoBigin.org.ALL - ZohoBigin.bulk.ALL - ZohoBigin.notifications.ALL - ZohoBigin.change_owner.CREATE - ZohoBigin.send_mail.all.CREATE - ZohoBigin.Files.CREATE - ZohoFiles.files.ALL ## Verify PopMCP shows Zoho Bigin as Connected under your organization's name, and zoho_bigin_get_org returns your organization while zoho_bigin_list_team_pipelines lists your pipelines and stages. ## Troubleshooting ### "Zoho did not accept the Client ID and Client secret for the United States data center" Cause: The client was created in another data center's console, such as api-console.zoho.eu, while **Zoho data center** was left empty, or one of the values was mistyped. Fix: Type that data center (EU, IN, AU, JP, CA, SA or CN) into **Zoho data center** under **More options**, or turn on Multi-DC on the client's **Settings** tab. Recopy both values from the **Client Secret** tab. ### "Zoho rejected the redirect URI" Cause: The client's **Authorized Redirect URI** does not exactly match PopMCP's callback. Fix: Open the client in the API Console, correct **Authorized Redirect URI** on the **Client Details** tab to `https://app.popmcp.com/api/providers/zoho-bigin/callback`, save, and connect again. ### "The Zoho sign-in expired before it could be completed" Cause: Zoho's authorization codes are short-lived, and the consent screen was left open too long. Fix: Click **Sign in with Zoho** again and accept the consent screen without waiting. ### "Zoho signed you in, but Bigin refused the request" Cause: You signed in with a Zoho account that has no Bigin organization in that data center. Fix: Sign in with the Zoho account you use for Bigin. If you use more than one Zoho data center, check that the client is enabled for the one your Bigin organization is in. ### "Your Bigin profile is not allowed to use the API, or the trial has ended" Cause: The person who signed in lacks the privilege in Bigin, or the organization's trial is over. Fix: Ask a Bigin administrator to check your profile and the organization's plan, or connect as an administrator. ### "This connection's Zoho sign-in does not include the permission for this call" Cause: The connection was made without that permission, for example a read-only sign-in trying to write. The message names the permission. Fix: Allow write actions on the connection in PopMCP if this is a write, or connect Zoho Bigin again and accept every permission. ### "Zoho no longer accepts this connection's authorization" Cause: The app was removed under Connected Apps, or more than 20 connections were made for the same Zoho user and client, which retires the oldest. Fix: Disconnect Zoho Bigin in PopMCP and connect it again. --- Source: https://www.docs.popmcp.com/docs/integrations/zoho-bigin/