Connecting Zoho Recruit

#Why Zoho Recruit customers ask for this

Zoho Recruit rarely turns up on its own. It is one product in a suite, and organisations that choose it usually run two or three of its siblings alongside — the CRM, the mail, the finance side — because they would rather hold a small number of tools that already know about each other than a long list that does not. That preference is the whole reason this page exists. A team which has deliberately consolidated does not want CV formatting to become the one job that happens somewhere else, in an unlogged browser tab, with the finished file carried back by hand.

The teams asking also tend to be small: an agency of a handful of consultants, or one or two internal recruiters in a growing company. There is rarely a developer to spare, which is why our team does the building and the configuring rather than yours, and why there is nothing left for anyone to maintain once it is on.

#What changes day to day

With the connection running:

1. Your recruiters carry on in Zoho Recruit, on the candidate records they already keep there.
2. The CV is rendered into your branded template, through the same editor and the same options as any other RemakeCV job.
3. The branded version is filed back against the candidate, so whoever opens that record next finds it waiting.

The middle step is ordinary RemakeCV, so nothing your team has already learned goes stale. See uploading a CV and reviewing and editing.

#Does the integration change the formatting?

No. The templates, the editor, anonymisation, summaries and downloads all behave the same way whether a CV came over a connection or was dragged into the browser. A connection settles the route the file takes and nothing about the document at the end of it — which is what makes it safe to add later, once your output is already agreed. Smaller teams frequently do exactly that: work standalone for a few weeks, settle what the branded CV should look like, then connect. Where the template itself has not been built yet, our team builds it to your own design; see requesting a custom template.

#Getting it built

The reach of any connection is set by the API access your provider grants, so we agree the scope before writing code rather than promising it here:

1. 1

   Tell us Zoho Recruit is where your candidates live

   Email support@remakecv.com with your organisation name and a short picture of today's path: who prepares candidate CVs, and where the branded document has to end up.

2. 2

   Arrange API access on your account

   Whoever administers Zoho Recruit for you asks Zoho what credentials can be issued and on what terms. Their answer defines what we build against.

3. 3

   Get the credentials to us on a secure channel

   We will point you to one. Anything with reach into candidate records deserves the handling you would give a password — not plain email, and not left sitting in a shared inbox.

4. 4

   We build it and switch it on

   Our team implements the connection and enables it for your company. The relevant controls appear in your RemakeCV dashboard afterwards, with nothing to install on anyone's machine.

Worth settling early: whether the connection is held once for the company or made by each recruiter individually. Which shapes are available depends on your account, and we tell you at scoping rather than choosing for you.

#The rest of your stack

Zoho Recruit is unlikely to be the only system a candidate document touches, and RemakeCV is not confined to the platforms with a live integration today — whatever else your organisation runs, our team can build against it once the provider issues credentials. If you do have engineering capacity and would rather own the connection, the public REST API exposes the processing, retrieval and template endpoints directly; connecting RemakeCV to any ATS or internal system covers what they reach. Either route is included on the Business and Enterprise plans without distinction — see plans and pricing.

#Start the conversation

Email support@remakecv.com with Zoho Recruit and your organisation name. We will confirm what the integration will do on your account, what we need from you, and how your recruiters will use it day to day.