Integrations: connect CVPitch to the tools your desk already uses

CVPitch integrations fit around the tools your agency already uses. You can pull CVs in from your ATS or CRM or by email, attach approved files back to the candidate's record, let AI assistants work with your submissions, get your team notified in chat, and connect your own systems through the API. This page lists every integration with its honest status and a setup outline. Technical details are on the developers page.

One rule applies to all of them: no integration can approve a submission. Approval always belongs to a recruiter in CVPitch, tied to the exact revision, template version and contact-removal policy.

Integration status at a glance

ATS and CRM connectors

A workspace owner connects each system once. After that, any recruiter can:

1. Import a CV. Choose Import from ATS on the submissions page, pick the connected system, search by name or email, choose the candidate and the CV or attachment (up to 10 MB), and import it. It is processed like any other upload, and importing the same file twice opens the existing draft.
2. Review and approve the CV in CVPitch as usual.
3. Attach the approved files back. From the export, choose Attach to ATS or CRM, tick PDF, DOCX or both, and send. The candidate is filled in from the import; otherwise search for them. Each file's status is shown.

Attach-back adds the approved files to the candidate's record; it never replaces the candidate's original or parsed resume. If a vendor does not answer clearly, for example after a timeout, CVPitch marks the send as uncertain and asks before sending again, so you do not get duplicate files.

Manatal is import-only because its upload API needs a public link to the file, and CVPitch never publishes candidate files on public links. SmartRecruiters search returns only candidates who have applied to at least one job.

These connectors are new. Each was built and tested against the vendor's published API documentation, not yet against live accounts in every system, so run a test import with your own credentials before relying on it, and tell us if anything behaves differently. Credentials are encrypted at rest, tested before they are saved and never shown again. Your ATS vendor may require a plan that includes API access.

Coming soon: Bullhorn, JobAdder, Vincere, Loxo and Zoho Recruit

These vendors approve third-party apps before they can connect to customer accounts. The connectors are waiting on that approval or registration, so they are not available yet. Until then, most agencies download the approved files and attach them in their ATS, or automate the round trip through the API, webhooks or a Zapier, Make or n8n workflow. If you use one of these systems, contact us and we will tell you when it is ready. Read more about applicant tracking systems and recruitment CRMs.

Format CVs by email

A workspace owner turns on a private intake address in Integrations and chooses the default client template and what the reply contains. Recruiters forward CVs to it from their own work mailbox:

• each attachment (up to 10 per email, 10 MiB each, in any supported format, including scans and photos) becomes a draft submission;
• one reply lists a review link for each file and a plain reason for any file that could not be processed;
• optionally, after approval and export, the final DOCX and PDF are emailed back to the colleague who sent the CV.

Only workspace members and up to 20 addresses the owner allows can use the address, and the sender's domain must pass DMARC; most business email services support this, and your IT administrator can confirm a DMARC record is published. Unknown, unauthenticated and automated mail is ignored without a reply. The owner sees a log of recent emails with their outcome, and can rotate the address at any time. The email's subject and body are not stored. Inbound and outbound mail is handled by our email provider, Resend.

Claude and ChatGPT through MCP

CVPitch runs a remote Model Context Protocol server at https://cvpitch.app/mcp. Once connected, your assistant can:

• search and list submissions and check their status, without candidate names or CV text;
• summarise the workspace, and check processing jobs, exports and usage;
• read selected candidate facts with their evidence, only if a workspace owner has turned on the sharing policy and a current privacy-checked preview exists;
• create a draft preview, or a short-lived link that opens the upload screen for you;
• export a submission a recruiter has already approved;
• create a short-lived download link for an approved file;
• suggest changes, which are staged for a human to review and accept.

It can never approve a submission, and it never receives recruiter notes or raw source text. Anything a tool returns is processed by your assistant's provider, which is why candidate evidence is off until an owner enables it.

Setup outline:

1. In Claude or ChatGPT, add a custom connector and enter https://cvpitch.app/mcp. Menu names vary by product and plan; on business plans an administrator may need to allow custom connectors.
2. Sign in to CVPitch when prompted. The consent screen shows the workspace and the permissions requested.
3. Choose Allow. You can revoke the connection from CVPitch at any time.
4. To let the assistant read candidate evidence, a workspace owner turns on the sharing policy in CVPitch and chooses what is masked.

Read our guide to connecting recruitment software to Claude and ChatGPT.

REST API and API keys

The REST API lives at https://cvpitch.app/integrations/v1. Workspace owners create scoped API keys that grant only the permissions an integration needs, such as reading metadata or uploading CVs. Keys are shown once, stored hashed and can be revoked. Third-party apps can also use OAuth 2.1 with PKCE. Uploads accept the same file types as the app, including scans and photos. Every endpoint, scope and limit is documented on the developers page.

Signed webhooks

Webhooks send an HTTPS POST to your endpoint when something happens, for example:

• a submission is ready for review;
• a submission is approved;
• an export is completed;
• approved files are attached to a candidate in a connected ATS or CRM;
• a share link is created, viewed or receives client feedback;
• a client sends an enquiry from your talent page;
• a processing job is queued, starts, finishes, is cancelled or fails.

Each delivery carries IDs, statuses and timestamps only, never candidate text, and is signed with HMAC-SHA256 so you can verify it came from CVPitch. Failed deliveries are retried a limited number of times. Destinations must be HTTPS addresses on the public internet.

Chat notifications: Slack, Teams, Discord and Google Chat

Get a message in the channel your desk watches when a CV is ready for review, approved, exported, or opened and answered by a client. Messages contain metadata and a link back into CVPitch only, never CV text.

Setup outline:

1. Create an incoming-webhook URL in your chat app: a Slack incoming webhook; a Teams channel webhook (Teams now creates these through its Workflows app, so check Microsoft's current instructions); a Discord channel webhook under the channel's Integrations settings; or a Google Chat space webhook.
2. In CVPitch, a workspace owner opens Integrations, chooses the app, pastes the URL and picks the events.
3. Send a test message, then treat the URL like a password: anyone who has it can post to that channel.

Zapier, Make and n8n recipes

CVPitch does not yet have published Zapier, Make or n8n apps. Instead, use each platform's generic webhook trigger and HTTP request action with a CVPitch API key. Some recipes agencies set up:

• Approved CV to a system without a native connector. Trigger on the "submission approved" or "export completed" webhook, request a download link from the API, fetch the DOCX or PDF, and attach it to the candidate record.
• New CVs from a shared folder. Watch a Google Drive, OneDrive or Dropbox folder, and send each new file to the API's document upload endpoint with an idempotency key.
• Client responses to a tracker. Trigger on share-link feedback and add a row to a sheet or update a deal stage.
• Daily usage report. On a schedule, read workspace usage from the API and post a summary to email or chat.

In Zapier, use Webhooks by Zapier (check your Zapier plan includes it). In Make, use a custom webhook and the HTTP module. In n8n, use the Webhook and HTTP Request nodes. To check signatures, add a code step that verifies the HMAC as described on the developers page.

Interview transcripts from Zoom, Teams and Google Meet

After a screening call, export the transcript and import it into the candidate's submission:

• Zoom and Microsoft Teams can provide transcripts as .vtt files.
• Google Meet saves transcripts as a Google Doc, which you can download as plain text (.txt).

CVPitch asks you to confirm you have permission to use the transcript. Selected notes are added as labelled recruiter notes for you to accept, separate from the facts extracted from the CV. There is no live connection to your meeting account.

Lever for MCP and API tools

Separately from the in-app connector above, an owner can save a Lever API key for the MCP tool and API endpoints that import a selected Lever attachment and attach an approved file back to an opportunity. Attach-back through these tools is never retried automatically if the result is uncertain, to avoid duplicate files.

How integrations protect candidate data

• Credentials are scoped, shown once, and stored hashed or encrypted. OAuth tokens are short-lived.
• ATS connectors move only the CV you choose to import and the approved files you choose to send, to the system you connected. File downloads are limited to 10 MiB and to the file hosts each vendor uses.
• Email intake accepts only authenticated mail from people you allow, and sends final files only to active members of your workspace.
• Notifications and webhooks carry metadata only.
• Candidate evidence reaches an AI assistant only when a workspace owner has enabled sharing, and recruiter notes are always withheld.
• Download links for approved files expire after five minutes and only work for the credential that created them.
• Webhook destinations must be public HTTPS endpoints; private network addresses are refused.

More on our security page. All integrations are included on every plan; see features and pricing.

Frequently asked questions

Can Claude or ChatGPT approve a CV in CVPitch?

No. Assistants can list, check, preview, suggest changes and export CVs a recruiter has already approved. Approval is a human action in CVPitch.

Do you have a Bullhorn integration?

A native Bullhorn connector is coming soon; it needs Bullhorn's partner approval before we can switch it on. Until then, use the REST API and signed webhooks directly, or through Zapier, Make or n8n, to move approved files and status updates.

Which ATS connectors can I use today?

Greenhouse, Lever, Workable, Ashby, Teamtailor, Recruitee, SmartRecruiters, Recruit CRM and Crelate for import and attach-back, and Manatal for import. Each uses API credentials from your own account.

Can I send CVs to CVPitch by email?

Yes. Turn on your workspace's private intake address and forward CVs to it from your work mailbox. You get review links back, and optionally the final files after approval.

What data do chat notifications include?

Metadata only: the event, IDs, statuses and a link back into CVPitch. Candidate names and CV text are never included.

Do integrations cost extra?

No. Every plan includes every integration and unlimited users, though your ATS vendor may charge for API access on its side. Start a free trial to try them.