Nava Go Integrator error when authorizing connection to Zoho CRM

Voiceware offers a solution named Nava Go Integrator to its clients. This app, as the name suggests, makes the integration between our systems and Zoho CRM possible. 

Sometimes, users will encounter an issue where they cannot authorize the connection between Nava Go Integrator and Zoho CM despite using their correct credentials.

To solve this problem follow the next steps:

1- Browse to https://api-console.zoho.com and log in with your Zoho details.

2. Click "Add Client".

3. Select a "Server-Based Application" client.

4. Enter your company URL, and then set the Authorized Redirect URL as

http://localhost/ under the heading "Client Details".

5. Click Save or Update, and copy the Client ID and Client Secret under the heading "Client Secret" to the Integrations Zoho CRM page on the Nava Go Integrator Settings for Zoho CRM.

6. Tick Data centers you want to access under the heading "Settings"."

7. Open Nava Go Integrator Configuration's Page.

8. Click on Integrations section over Zoho CRM Integration.

********** Note: If you dont have any integrations yet click Add New on the Integrations Page and select Zoho CRM. ********

• Related Articles

• How to access Voiceware Phone System

  To access Voiceware Phone System the users should go to the following link: Voiceware Phone System Link - https://voiceware.simplelogin.net

• How to use SNAP.GO Webphone using Voiceware Portal

  Voiceware offers a webphone phone app to all of its users. This gives you the ability to work remotely, out of a physical location, while still having your office phone number in your webphone app when dialing out to prospects, clients or patients. ...

• Star Codes for Voiceware Phone System

  Overview Listed below are the default feature codes available to all Users. Most codes begin with a star key followed by 2-3 digits. Please note that certain extension numbers should NOT be used as they may conflict with default features. To use any ...

• API Error 500 Fails in Production Due to Large Response Size

  Summary An API endpoint may work correctly in a development environment but fail in production with 500 Internal Server Error when the response payload is too large. In this case, the endpoint was returning a very large JSON response containing full ...

• Phone not registering after standard troubleshooting steps

  SIP phones communicate with our Registration Server (NDP) server using the UDP (User Datagram Protocol ) protocol. I have found that, in 2 different locations of one of our clients, the phones won't register with this standard type of protocol ...