--- title: Zoho Bigin API Integration on Truto slug: zohobigin category: CRM canonical: "https://truto.one/integrations/detail/zohobigin/" --- # Zoho Bigin API Integration on Truto **Category:** CRM **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. ## MCP-ready AI tools Truto exposes 7 tools for Zoho Bigin that AI agents can call directly. - **list_all_zohobigin_users** — A user is someone who has access to an organization in Bigin. Use this endpoint to get all users in the Zoho Bigin account. - **get_single_zohobigin_user_by_id** — Use this endpoint to get a single user in the Zoho Bigin account. It always requires the ID to fetch. - **delete_a_zohobigin_user_by_id** — Use this endpoint to delete a single user in the Zoho Bigin account. It always requires the ID to delete a user. - **list_all_zohobigin_current_organization** — An organization in Bigin represents a company. Use this endpoint to get the current company information in the Zoho Bigin account. - **list_all_zohobigin_me** — Use this endpoint to get the information about the currently authenticated user in the Zoho Bigin account. - **list_all_zohobigin_roles** — In Zoho Bigin, each organization has a defined set of roles that determine data access based on a hierarchy. These roles are assigned to users according to their responsibilities. Use this endpoint to retrieve a list of all the roles available in your organization. - **list_all_zohobigin_profiles** — In Bigin, profiles determine user permissions and control the actions users can perform within the application. Each user in the Bigin setup is assigned a profile that defines their level of access to organizational data. Use this endpoint to retrieve a list of all the profiles available in your organization. ## How it works 1. **Link your customer's Zoho Bigin account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Zoho Bigin.** The Proxy API is a 1-to-1 mapping of the Zoho Bigin API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Map dialer seats to CRM reps for automatic call logging** — VoIP and conversational AI platforms can fetch Zoho Bigin users and roles to map their dialer seats to the correct CRM reps, ensuring call logs and follow-up tasks land on the right person's record without manual configuration. - **Enforce CRM visibility rules in third-party tools** — SaaS products that surface CRM data — like support desks or reporting dashboards — can sync Bigin roles and profiles to respect the organization's data access hierarchy, so a junior rep only sees contacts and deals they own. - **Automate lead assignment with round-robin based on active users** — Marketing automation and lead capture platforms can pull the list of active Bigin users and their roles to implement fair, role-aware lead routing when creating deals or contacts from inbound campaigns. - **Verify org identity for multi-tenant onboarding flows** — SaaS companies serving agencies or multi-org businesses can query the current Bigin organization to confirm which company instance the end user is connecting, preventing data from being written to the wrong account. - **Sync user directories for seat-based provisioning and billing** — Platforms that bill per-seat or need to provision users can sync the Bigin user directory to automatically match licensed seats, deactivate removed users, and keep identity records in lockstep. ## What you can build - **CRM user-to-app seat mapping UI** — Let your customers connect their Bigin account and visually map each Bigin user to a corresponding seat in your product, powered by list_all_zohobigin_users. - **Role-aware data access layer** — Fetch Bigin roles and profiles to dynamically scope what data each connected user can see inside your application, mirroring the CRM's permission hierarchy. - **Org verification step in your onboarding wizard** — Display the connected Bigin organization's name and details during setup so end users can confirm they're linking the correct company instance before any data syncs. - **Automated user deprovisioning webhook** — Periodically poll Bigin users and compare against your own user list to flag or deactivate seats when a CRM user is removed, using delete_a_zohobigin_user_by_id for cleanup workflows. - **Current-user context for embedded widgets** — Use list_all_zohobigin_me to identify the authenticated Bigin user and personalize embedded UI components — like showing 'Logged in as Jane, Sales Manager' inside your app. - **Unified user directory dashboard** — Ship a single admin panel that lists all CRM users, their roles, and their profiles across every connected integration, with Zoho Bigin as a first-class source via Truto's Unified User Directory API. ## FAQs ### What authentication method does the Zoho Bigin integration use? Zoho Bigin uses OAuth 2.0. Truto handles the full auth flow — token generation, refresh, and secure storage — so your team never manages credentials directly. ### Which Zoho Bigin resources can I access through Truto today? You can list, get, and delete users; list the current organization; retrieve the authenticated user's own record (me); and list all roles and profiles. These map to Truto's Unified User Directory API for Users and Roles. ### Does the integration handle Zoho Bigin's API rate limits? Yes. Truto manages rate limiting, retries, and pagination automatically, so your application doesn't need to implement back-off logic or cursor tracking against Bigin's API quotas. ### Can I use the Unified User Directory API across Zoho Bigin and other CRMs? Absolutely. Truto's Unified User Directory API normalizes Users and Roles into a common schema. You write one integration and it works across Bigin, Zoho CRM, HubSpot, Salesforce, and other supported connectors. ### How do profiles differ from roles in Zoho Bigin? Roles define the data visibility hierarchy (e.g., Manager can see their reports' records), while Profiles define feature-level permissions (e.g., which modules a user can access). Both are available via list_all_zohobigin_roles and list_all_zohobigin_profiles respectively. ### Can I access CRM entities like Deals, Contacts, or Pipelines through this integration? The currently available tools focus on the User Directory — users, roles, profiles, organization, and the authenticated user. If you need CRM entity endpoints like Deals or Contacts, contact Truto to discuss enabling additional resources for Zoho Bigin.