Deployment Guide

The deployment guide for the Genesys Contact Center in ZOHO CRM provides instructions to install, configure, and use the connector within ZOHO environments.

Intended Audience

This document outlines the deployment of a ZOHO-Embedded Genesys connector.

Prerequisites

The following are the prerequisites for the deployment of the Zoho Connector for Genesys Cloud.

1. You must have Zoho and Genesys CC. 

2. A Zoho CRM account is required.

3. The user must have administrative rights.

4. Genesys Generic connector should be deployed. If not, see Genesys Generic Connector Deployment Guide.

Install Zoho Genesys Extension

1. Use the URL to install the Zoho-Genesys Extension.

2. Accept all required permissions and select the “Install for all users” option in the installation wizard.

3. The extension will then begin installing and notify you once complete.

Zoho Connector Deployment

Before you begin, verify that on the server, you have:

• Installed Kubernetes. If not, see Deployment Planning

• Setup storage. If not yet, see Storage Solution - Getting Started

Pulling the Zoho Generic Connector from Git

1. Create a directory with name as mkdir zoho-connector or according to your ease.

2. Navigate to newly created directory by cd zoho-connector.

3. Pull the the code from the:

git clone --branch k8s-v1.0 --single-branch https://gitlab.expertflow.com/cti/zoho-crm-generic-connector.git

4. Run cd zoho-crm-generic-connector/kubernetesto change directories. This is where all the YAML files are stored.

Setting Up Environment

Our server deployment is managed through Kubernetes, where the static files for the connector are hosted and the Zoho Connector runs.

Namespace

Create a namespace “expertflow” if it doesn’t exist.

kubectl create namespace expertflow

Configure Ingress.yaml

Zoho Generic Connector for Genesys cloud should be accessible by a fully qualified domain name. Assign the FQDN.

sed -i 's/devops[0-9]*.ef.com/<FQDN>/g' zoho-generic-connector-ingress.yaml

Create Self-Signed SSL/TLS Ingress Certificates (optional if already present)

1. Create IngressCerts directory (optional)

• mkdir ingress-certs  
  

1. cd ingress-certs
   

• set the Variable name to your FQDN (e.g. projectsdemo.expertflow.com).
  The ${FQDN} variable in following commands will be replaced with the value you provided in this step

• export FQDN=<enter FQDN here>
  

• Now generate a secret with the following commands.

• openssl req -x509 \ -newkey rsa:4096 \ -sha256 \ -days 3650 \ -nodes \ -keyout ${FQDN}.key \ -out ${FQDN}.crt \ -subj "/CN=${FQDN}" \ -addext "subjectAltName=DNS:www.${FQDN},DNS:${FQDN}" 
  

• Create a Kubernetes secret in your required namespace. In our case it’s expertflow

• kubectl -n expertflow create secret tls hs-ef-ingress-tls-secret --key  ${FQDN}.key --cert ${FQDN}.crt
  

Configure zoho-generic-ingress.yaml

• Open the zoho-generic-connector-ingress.yaml file.

• Replace the hosts and host value with the FQDN on which you are deploying the application.

• Set the path with a unique name for your sap connector.

• You have to replace the value for UNIQUE_NAME with the path which you will use for your application.

Configure zoho-generic-deployment.yaml

• Open the zoho-generic-connector-deployment.yaml file.

• Replace the image with the updated tag.

• Updated tag is 1.0.0

Applying Kubernetes YAMLs

• Apply the service with kubectl apply -f zoho-generic-connector-service.yaml

• Apply the image-pull secret with kubectl apply -f zoho-generic-connector-imagePullSecret-expertflow.yaml

• Apply the Ingress with kubectl apply -f zoho-generic-connector-ingress.yaml. (For RKE2-based Ingresses using Ingress-Nginx Controller)

• Apply the deployment with kubectl apply -f zoho-generic-connector-deployment.yaml

Set Variables in the Extension Settings

Launch Genesys App:

Go to the CRM dashboard, click the phone icon “📞” at the bottom, and open the Genesys Cloud app in Zoho CRM's softphone.