Zoho Bigin

Zoho Bigin is a pipeline-centric CRM built for small and micro businesses, helping teams manage contacts, companies, deals, tasks, and activities in one place. The Bigin REST API exposes these CRM records so they can be read from and written to programmatically. Nexla connects to the Bigin API using OAuth 2.0, letting you ingest records such as contacts, companies, and pipelines, and push new or updated records back into Bigin.

Power end-to-end data operations for your Zoho Bigin API with Nexla. Our bi-directional Zoho Bigin connector is purpose-built for Zoho Bigin, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Zoho Bigin or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Zoho Bigin workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Zoho Bigin uses OAuth 2.0 for API authentication. Before creating a credential in Nexla, register a client application in the Zoho API Console to obtain a Client ID and Client Secret, and identify the API Base URL for your account's data center.

To register a client and gather these values, follow these steps:

1. Sign in to the Zoho API Console with the Zoho account that has access to your Bigin organization.

2. Click Add Client and choose the Server-based Applications client type (appropriate for a server-to-server integration such as Nexla).

3. Enter a Client Name, a Homepage URL, and an Authorized Redirect URI. The redirect URI must match the OAuth callback that Nexla uses; use the redirect URI shown in the Nexla credential overlay when you create the credential.

4. Click Create. The console generates your Client ID and Client Secret. Copy and store both values securely, as the Client Secret is confidential.

5. Determine the Base URL for your account's data center. Zoho serves Bigin from region-specific API domains, for example https://www.zohoapis.com/bigin/v2 (US), https://www.zohoapis.eu/bigin/v2 (EU), https://www.zohoapis.in/bigin/v2 (IN), https://www.zohoapis.com.au/bigin/v2 (AU), https://www.zohoapis.jp/bigin/v2 (JP), or https://www.zohoapis.com.cn/bigin/v2 (CN). Use the domain that matches where your Bigin account's data resides.

6. Decide which OAuth scopes your integration needs. Bigin scopes follow the pattern ZohoBigin.modules.ALL for record access, ZohoBigin.settings.ALL for module metadata, and ZohoBigin.org.ALL for organization details. Request only the scopes required for the records you intend to move.

During credential creation in Nexla you will authorize the application through Zoho's consent screen, which grants Nexla an access token and refresh token used for subsequent API requests. For full details on client registration, scopes, and data center domains, see the Bigin API documentation.

Authenticate

Credentials required

An OAuth authentication flow where users must authorize an application to access their data

Field	Required	Secret	Description
Authorization URL	No	No	The URL endpoint where users authenticate and authorize access
Client ID	Yes	Yes	A unique public identifier assigned to your application
Access Scope	No	No	A space-separated list of permissions your application requests
Token URL	No	No	The URL endpoint where authorization codes are exchanged for access tokens
Client Secret	No	Yes	A private key used to authenticate your application when requesting tokens
Base URL	Yes	No	API base URL for this account/organization.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Client ID and Client Secret from the Zoho API Console. If your account uses non-default endpoints, confirm the Authorization URL and Token URL; the defaults point to Zoho's US accounts domain.

4. Enter the Base URL for your data center in the Base URL field, for example https://www.zohoapis.com/bigin/v2 for US-based accounts. Optionally set the Access Scope to the space-separated list of Bigin scopes your integration requires.

5. Complete the OAuth authorization flow when prompted. You will be redirected to Zoho to sign in and authorize Nexla; on success, Zoho returns an access token and refresh token that Nexla stores for subsequent requests.

   If your Client Secret is compromised, revoke the client in the Zoho API Console and generate new credentials. The access token grants access to your Bigin data based on the scopes you authorized and should be treated as sensitive information.

   For detailed information about OAuth registration, scopes, data center domains, and available endpoints, see the Bigin API documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Zoho Bigin connector tile, then select the credential that will be used to connect to the Zoho Bigin instance, and click Next; or, create a new Zoho Bigin credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Zoho Bigin endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

List Users

Retrieve users.

• This endpoint template fetches user records from your Bigin organization. Results are paginated, and Nexla automatically advances through pages until all available records have been retrieved.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Contacts

Retrieve contacts.

• This endpoint template fetches contact records from the Contacts module. Results are paginated, and Nexla automatically advances through pages until all available records have been retrieved.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Modules

Retrieve modules.

• This endpoint template fetches the list of modules configured in your Bigin organization. It returns a single, static response and is not paginated.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Organizations

Retrieve organizations.

• This endpoint template fetches organization details for your Bigin account. It returns a single, static response and is not paginated.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Notes

Retrieve notes.

• This endpoint template fetches note records from the Notes module. Results are paginated, and Nexla automatically advances through pages until all available records have been retrieved.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Tags

Retrieve tags.

• This endpoint template fetches the tags defined in your Bigin organization. It returns a single, static response and is not paginated.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Companies

Retrieve companies.

• This endpoint template fetches company records from the Accounts module. Results are paginated, and Nexla automatically advances through pages until all available records have been retrieved.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Tasks

Retrieve tasks.

• This endpoint template fetches task records from the Tasks module. Results are paginated, and Nexla automatically advances through pages until all available records have been retrieved.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Events

Retrieve events.

• This endpoint template fetches event records from the Events module. Results are paginated, and Nexla automatically advances through pages until all available records have been retrieved.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Products

Retrieve products.

• This endpoint template fetches product records from the Products module. Results are paginated, and Nexla automatically advances through pages until all available records have been retrieved.

For detailed information about the response structure and available fields, see the Bigin API documentation.

List Pipelines

Retrieve pipeline (deal) records, Bigin's primary sales-tracking object.

• This endpoint template fetches pipeline records from the Pipelines module, Bigin's core sales-tracking object. Results are paginated, and Nexla automatically advances through pages until all available records have been retrieved.

For detailed information about the response structure and available fields, see the Bigin API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Zoho Bigin data sources can also be manually configured to ingest data from any valid Bigin API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Zoho Bigin data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Zoho Bigin destination, and select the Send to Destination option from the menu. Select the Zoho Bigin connector from the list of available destination connectors, then select the credential that will be used to connect to the Zoho Bigin organization, and click Next; or, create a new Zoho Bigin credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Zoho Bigin endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Contact

Create one or more contact records in Bigin.

• This endpoint template sends records from a Nexset as JSON to the Contacts module to create new contacts. Ensure each record contains the fields required by the Bigin Contacts module.

For detailed information about request body formats and available fields, see the Bigin API documentation.

Update Contact

Update one or more existing contact records in Bigin.

• This endpoint template sends records from a Nexset as JSON to update existing contacts in the Contacts module. Each record must include the Bigin record ID of the contact being updated.

For detailed information about request body formats and available fields, see the Bigin API documentation.

Create Company

Create one or more company (account) records in Bigin.

• This endpoint template sends records from a Nexset as JSON to the Accounts module to create new companies. Ensure each record contains the fields required by the Bigin Accounts module.

For detailed information about request body formats and available fields, see the Bigin API documentation.

Create Task

Create one or more task records in Bigin.

• This endpoint template sends records from a Nexset as JSON to the Tasks module to create new tasks. Ensure each record contains the fields required by the Bigin Tasks module.

For detailed information about request body formats and available fields, see the Bigin API documentation.

Delete Record

Delete one or more records from a specified Bigin module by record ID.

• This endpoint template deletes records from a target Bigin module. The module API name is supplied as part of the request, and each record must reference the Bigin record ID to be deleted.

For detailed information about deleting records, see the Bigin API documentation.

Create Pipeline

Create a new pipeline (deal) record in Bigin.

• This endpoint template sends a record from a Nexset as JSON to the Pipelines module to create a new pipeline (deal). Ensure the record contains the fields required by the Bigin Pipelines module.

For detailed information about request body formats and available fields, see the Bigin API documentation.

Manual configuration

Zoho Bigin destinations can also be manually configured to send data to any valid Bigin API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Zoho Bigin APIs expect JSON format for write operations. For update and delete operations, include the Bigin record ID for each record so the API can target the correct object.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Zoho Bigin endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Zoho Bigin endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.