×îв©²ÊÍøÕ¾

Node.js SDK for ×îв©²ÊÍøÕ¾ CRM APIs

The Node.js SDK for ×îв©²ÊÍøÕ¾ CRM allows developers to easily create Node.js applications that can be integrated with ×îв©²ÊÍøÕ¾ CRM. It serves as a wrapper for the ×îв©²ÊÍøÕ¾ CRM REST APIs, making it easier to access and utilize the services of ×îв©²ÊÍøÕ¾ CRM.

Authentication to access the CRM APIs is facilitated through OAuth2.0, and the authentication process is streamlined through the use of the Node.js SDK. The grant and access/refresh tokens are generated and managed within the SDK code, eliminating the need for manual handling during data synchronization between ×îв©²ÊÍøÕ¾ CRM and the client application.

The latest version of Node.js SDK () supports version 8 of ×îв©²ÊÍøÕ¾ CRM APIs. For more information on the released Node.js SDK versions, refer here.

Prerequisites

  • Ensure that the client app has Node version 14.21.3 or above.
  • An IDE such as Visual Studio Code or Eclipse
  • ×îв©²ÊÍøÕ¾ CRM account.

Step 1: Register your application

Before you get started with authorization and make any API calls using the ×îв©²ÊÍøÕ¾ CRM Node.js SDKs, you need to register your application with ×îв©²ÊÍøÕ¾ CRM.

  1. Go to and click on Add Client
  2. Choose the client type as Self Client or Server-based Applications depending on your requirements.
  3. Enter the required credentials.
  4. Click CREATE
  5. Make a note of the Client ID and Client Secret generated for your application.

register a client

Step 2 : Create a project and add NodeJS SDK in your project.

In this step, you'll create a new project in your preferred IDE and add the NodeJS project in your project. We will be using Visual Studio Code IDE in this guide.

  1. Create a project in your preferred IDE
  2. Install NodeJS SDK. Run the following command in the workspace terminal to install V8 SDKs: npm install @zohocrm/nodejs-sdk-8.0
  3. Add the following line to your package.json file to include make use of the ES modules : "type" : "module".

create Nodejs project and add dependencies

Step 3 : Generation of Grant token

Generate a grant token from the ×îв©²ÊÍøÕ¾ API Console by following the steps described in this page.

generate grant token

Step 4:

In the configuration step, you will set up details such as user authentication, environment, , logging, and API call timeout settings. The following table gives the details of all the keys you can configure, with detailed explanation.

KeyDescriptionSample

environment

mandatory

Represents the domain information to make API calls in Domain.Environment pattern.
Domains: USDataCenter, EUDataCenter, INDataCenter, CNDataCenter, AUDataCenter
Environments: PRODUCTION(), DEVELOPER(), SANDBOX()
environment = USDataCenter.PRODUCTION;

token

mandatory

Contains user token details. Depending on the tokens, you can choose grantToken flow, refreshToken flow, or accessToken flow. token= new OAuthToken.Builder()
.clientID("clientId")
.clientSecret("clientSecret")
.grantToken("grantToken")
.redirectURL("redirectURL")
.build();

logger

optional

Contains the configuration for logging exceptions and API call information. By default, the logs will be available in the workspace as sdk_logs.log. logger = new Logger.Builder()
.level(Levels.INFO)
.filePath("/Users/nodejs_sdk_log.log")
.build();

store

optional

Contains details for the Token Persistence object. You can choose between DB Store, File Store, or Custom Store and configure accordingly. To know more about token persistence, refer . tokenstore = new DBStore.Builder()
.host("hostName")
.databaseName("databaseName")
.tableName("tableName")
.userName("userName")
.password("password")
.portNumber("portNumber")
.build();

SDKConfig

optional

Contains additional configuration details like timeout, autorefresh fields, picklistvalidation, etc. sdkConfig = new SDKConfig.Builder()
.autoRefreshFields(false)
.pickListValidation(true)
.build();

resourcePath

optional

The path containing the absolute directory path to store user-specific files containing the module fields information.

The field metadata for the current user will be fetched and saved in the JSON file. Whenever a user performs a record operation, the data types, picklist values, unique fields etc in the input will be validated against the field metadata stored in the JSON file. In case the user tries to perform a record operation with wrong pick list values, or wrong datatype, it will be caught during this validation stage, and the SDK will throw an error. This will ensure that credits are not consumed for such operations that would anyway result in a failure. In addition to this, the response will also be parsed in the correct format depending on the data in the JSON file.
String resourcePath = "/Users";

For detailed instructions on how to configure the above keys and get started, refer . Find a sample code for initialization .

SDK initialization

Step 5 : Making requests using Node.js SDK

After you have configured and initialised, you can start making your requests using Node.js SDK and utilise the functionalities of ×îв©²ÊÍøÕ¾ CRM. is a sample code to insert a new record in to the Leads module.

Note:

  • Node.js's default execution model is asynchronous. However, our SDK supports synchronous operations. To invoke our SDK methods synchronously, use the await keyword as demonstrated in the . Failure to do so will result in an error.

Making API calls

Responses and Exceptions

When working with the ×îв©²ÊÍøÕ¾ CRM Node.js SDK, it is important to understand the responses and exceptions that can be encountered during API calls.

Note:

  • The APIResponse object holds the results of your request. You can access the actual response data using the getObject() method.
  • The APIResponse<ResponseHandler>and APIResponse<ActionHandler> are the common wrapper objects for handling responses from ×îв©²ÊÍøÕ¾ CRM APIs. This depends on the API. For more details, refer .
  • APIException: This exception is thrown for errors that are related to the API itself, such as authentication errors or invalid request parameters.
  • SDKException: This exception is thrown for errors that are related to the ×îв©²ÊÍøÕ¾ CRM SDK, such as network errors or SDK implementation errors.

For more details on the Responses and Exceptions, refer .

Older versions

v7 APIs â–¶

v6 APIs â–¶

v5 APIs â–¶

v3 APIs â–¶

v2.1 APIs â–¶
v2 APIs â–¶