Integrating SailPoint with Bigin
This document provides instructions to configure a new direct connection between SailPoint and Bigin.Bigin is a pipeline-centric customer relationship management (CRM) platform by Zoho that allows organizations to securely manage customer interactions, sales pipelines, and team operations. It provides a streamlined environment where teams can automate sales workflows, track deals across various stages, and manage user access in a centralized space. Bigin offers a robust REST API for retrieving key identity data such as users, profiles, and roles. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.
Note
To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.
Supported Features
The Bigin connector supports the following:
Account Management
- Aggregate all users from Bigin
Important
Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
- Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
- Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.
These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.
Entitlement Management (Roles)
- Aggregate Roles
Supported Managed Systems
- Bigin
Prerequisites
Ensure the following prerequisites are met before proceeding with the configuration:
- Bigin Account: You have access to a Bigin by Zoho CRM instance.
- Administrator Access: You have an administrator account in Bigin to generate OAuth credentials.
- Zoho API Console Access: You have registered an application in the Zoho API Console to obtain OAuth 2.0 credentials.
- Client ID: Obtained from the Zoho API Console after registering your application.
- Client Secret: Obtained from the Zoho API Console after registering your application.
- Refresh Token: Generated via the Zoho OAuth 2.0 authorization flow with the required scopes.
API Authentication
The connector uses OAuth 2.0 with a refresh token grant type for authentication. The connector automatically obtains an access token using the provided refresh token, client ID, and client secret.
To generate your OAuth credentials:
- Sign in to the Zoho API Console.
- Click Add Client and select Server-based Applications.
- Fill in the required details (Client Name, Homepage URL, Authorized Redirect URI).
- Copy the generated Client ID and Client Secret.
-
Generate a Refresh Token using the OAuth 2.0 authorization flow with the following scopes:
ZohoBigin.users.ALLZohoBigin.settings.roles.ALL
Note
The refresh token does not expire unless explicitly revoked. However, if you regenerate it, the previous token becomes invalid. Store it securely.
Required Permissions
- The OAuth application must be granted scopes to read users and roles.
- Minimum required scopes:
ZohoBigin.users.ALL- Required to aggregate all user accountsZohoBigin.settings.roles.ALL- Required to aggregate roles
- The user who generates the refresh token must have Administrator privileges in Bigin.