Integrations, API and Security

How does CloudHire handle integrations, API access and security?

CloudHire connects to the tools recruiting teams already use: Gmail for sending and replies, Google Calendar for scheduling, LinkedIn for messaging and outreach, and WhatsApp for two-way candidate threads, plus native two-way sync with 180+ ATS platforms. A public API with scoped keys and signed webhooks covers custom workflows, and access is governed by role-based access control, encryption in transit and at rest, and activity logging.

This guide is the factual map of what connects to what, what the API can do, and which security controls exist today versus which are planned. CloudHire's position on roadmap honesty is simple: live features are listed as live, beta as beta, planned as planned, so a security or IT review can rely on this page. It belongs to the CloudHire guides for businesses hub alongside guides on outreach, pipeline and sourcing.

Live integrations

Gmail

Gmail is the recruiter inbox integration: outreach and stage emails send from the recruiter's real address rather than a generic platform domain, and candidate replies flow back into CloudHire's unified inbox where they sit beside WhatsApp and in-app chat. Mailbox management is full-lifecycle, add a mailbox, configure it, disconnect it, and teams can run multiple mailboxes with per-job sender identity so each role's mail comes from the recruiter who owns it.

Google Calendar

Google Calendar powers interview scheduling. When a candidate reaches the interview stage of the pipeline, the booking flow works against the recruiter's actual calendar, keeping scheduled interviews visible in both systems.

LinkedIn

Recruiters connect a LinkedIn account for messaging and outreach: connection requests and messages run as sequence steps, with templates, per-job senders, and accept and reply rates tracked.

WhatsApp

WhatsApp handles both outbound outreach, via an approved business template, and two-way threads with 24-hour session handling and read receipts, all inside the same unified inbox as email and in-app chat. How these channels combine into sequences is the subject of the multi-channel candidate outreach guide.

Native ATS sync with 180+ platforms

Most teams adopting CloudHire already have a system of record, so CloudHire ships native ATS sync with 180+ ATS platforms. The sync is two-way and covers shortlists, pipeline stages and scorecards: shortlist a candidate in CloudHire and they appear in the ATS; move a stage in the ATS and CloudHire reflects it. A per-workspace switch controls whether sync is on at all, so a team can pilot CloudHire in isolation before mirroring anything into the corporate ATS.

The stages being synchronised are the three-phase pipeline described in the applicant tracking and hiring pipeline guide. The supported platform list and connection details live on the ATS integrations page.

The public API, webhooks and data portability

For workflows no prebuilt integration covers, CloudHire exposes a public API:

• Scoped API keys, so a key carries only the permissions its integration needs
• Rate limits that keep one integration from degrading the workspace
• Signed webhooks fired on pipeline events, letting external systems react to stage changes with verifiable payloads
• Documentation available in-app, alongside the public API reference
• An API-only workspace mode for teams that operate CloudHire entirely through their own software

Data also moves as files when that is simpler: CSV export gets analytics and candidate data out, and bulk resume import brings a ZIP of resumes in as parsed, scored candidates.

What teams typically build with it

Three patterns come up repeatedly. First, notification bridges: a signed webhook on a stage change posts to an internal channel, so the hiring squad hears about a new shortlist without opening CloudHire. Second, reporting pipelines: candidate and funnel data pulled into a warehouse on a schedule, joined against offer and retention data the recruiting tool never sees. Third, custom intake: a company's own careers experience submitting applicants into the CloudHire pipeline over the API, with the hosted application flow kept as a fallback. Because keys are scoped, each of these runs with its own minimal permissions, and revoking one integration never touches the others.

Integration and security status matrix

The honest, current status of every connection and control discussed on this page:

Security and access control

Role-based access control

CloudHire enforces role-based access control with three roles: Admin, Recruiter and Member. Each role bounds what a user can see and change, and audit events are recorded so administrative actions leave a trail. Combined with the pipeline's own audit of every candidate move, this means both people-actions and candidate-actions are reconstructable.

Data protection

Candidate data is encrypted in transit and at rest. Activity logging records what happens in the workspace, and data-retention controls let administrators govern how long candidate data is kept. For teams that want a minimal surface area, API-only workspace mode removes interactive access entirely and drives the workspace through scoped keys.

What is on the enterprise roadmap

Several enterprise controls are planned rather than live, and CloudHire says so plainly: SSO via SAML and OIDC with SCIM provisioning, custom roles beyond the built-in three, a white-label domain, custom SLA terms, DPA execution and formal security review support. If any of these gate your procurement, contact CloudHire sales for current timelines before you plan a rollout.

Team management

Administration scales with the team. Member management tracks seats as people join and leave, and jobs are assigned to recruiters either singly or in bulk, so ownership of every role is explicit. Domain-based workspace routing places new signups from your company's email domain into the correct workspace automatically, which prevents the stray-workspace sprawl that plagues self-serve tools.

Job assignment interacts with the integrations above in a useful way: because outreach supports per-job sender identity, assigning a job to a recruiter also determines whose mailbox and whose LinkedIn account represent that role to candidates. Ownership in CloudHire is therefore not just an internal label, it decides who the candidate actually hears from.

Analytics and visibility

The dashboard shows jobs, applicants, recent activity, pending actions and upcoming interviews in one view, so a hiring lead starts the day knowing what needs attention. Per-job funnel stats show how candidates flow through the pipeline stages for each role, which surfaces where each search is actually stalling: plenty of applicants but few shortlists points at sourcing quality, plenty of shortlists but few scheduled interviews points at outreach or scheduling. A usage page shows how the workspace consumes its plan, so there are no surprises at renewal. All of it exports to CSV, and anything deeper can be pulled over the API.

Evaluating CloudHire for your stack

A practical evaluation order: confirm your ATS is among the 180+ supported platforms, connect Gmail and Google Calendar for one pilot team, keep the workspace sync switch off until the pilot proves out, then turn on two-way sync and webhooks. Verified hiring via Cloud-ID and the trust reports from other teams in CloudHire case studies round out the picture.

For API credentials, ATS sync setup or a security questionnaire, talk to the CloudHire sales team, they will walk your IT reviewers through the controls above on a live workspace.