HR & Recruiting Connectors

A connector is a connection to data, not a magic button. It tells Claude where to read. Whether the output is useful still depends on what you ask and how you check the result.

HR has the smallest connector category in the catalog (about 8 tools) but the most impact per connector. Reviewing 200 applicants takes about 4 hours; Claude with the Workable or Indeed connector compresses it to 20 minutes of review plus a defensible audit trail. Interview transcripts that used to die in someone’s notebook become structured scorecards. The connectors below cover the recruiter funnel, the people-analytics layer, and the compensation layer.

What does the HR and recruiting category include?

• Applicant tracking and job posting. Workable, Indeed, ZipRecruiter, Dice. Read applicants, filter by criteria, draft outreach.
• Interview intelligence. Metaview. Pulls structured interview transcripts, extracts signals against your rubric.
• People analytics. Visier. Workforce data, attrition modeling, comp benchmarking.
• Equity and compensation. Carta. Option grants, vesting schedules, cap-table-aware compensation decisions.
• Talent acquisition specialty. Aura. Talent intelligence and competitive hiring signals.

Which HR and recruiting connector should I add first?

HR connectors should match your most-used hiring or people-data system. Pick one and start; this category does not need many connections to be useful.

1. Your ATS. Workable for SMB, Greenhouse or Lever (via partner connectors if available), Indeed if you post heavily, ZipRecruiter if you hire blue-collar or service roles.
2. Metaview. Only if you record interviews. The structured-feedback workflow is the single biggest hiring-quality lift available.
3. Visier. Only if you have enough headcount (~50+) for the people analytics to be meaningful.
4. Carta. Only if you have a cap table. Skip for non-equity orgs.

Standout prompts for the HR and recruiting stack

These are the prompts that exploit each connector’s specific capability rather than treating Claude like a generic chat tool. Copy, paste, modify the specifics to match your context.

• Candidate Batch Ranking. Reads the 50 most recent applicants for a role from Workable or Indeed, ranks against your scorecard, drafts the top-5 shortlist with explicit reasoning per candidate.
• Auto-Reject with Dignity. For applicants who clearly do not match the criteria, drafts a respectful rejection email that explains the specific gap (skill, location, experience) rather than a generic auto-reply.
• Outreach for Passive Candidates. Reads your sourced candidate list, drafts personalized first-touch emails grounded in the candidate’s specific background, not template language.
• Interview-to-Scorecard. Pulls a Metaview interview transcript, evaluates against the role’s scorecard, drafts the structured feedback the hiring committee needs.
• Reference Call Brief. Before a reference call, pulls the candidate’s resume plus interview notes, drafts five candidate-specific questions to ask.
• Offer Negotiation Decision Doc. Pulls comp data from Visier and equity scenarios from Carta. Drafts the one-page offer rationale with cash, equity, signing bonus tradeoffs.
• Attrition Risk Brief. Reads Visier; flags managers or teams trending toward higher-than-normal attrition, drafts the diagnostic questions for People Ops.
• Job Description Refresh. Reads an existing JD, compares against the actual interview rubric, surfaces where they have drifted apart, drafts the rewrite.
• Hiring Loop Calibration. Pulls Metaview transcripts from all interviewers on a recent loop, surfaces where interviewers disagreed most, drafts the calibration topic for the next training.
• Compensation Band Adjustment Brief. Reads Visier benchmarks plus recent offers accepted or declined. Drafts the case for adjusting a comp band, including the data points and the dollar impact.

How do I add the Workable connector?

1. In Claude, open the toolbox in the bottom-left, click Customize, then Connectors.
2. Click the +, then Browse connectors.
3. Search for Workable. Click + on the card.
4. Workable uses OAuth. Sign in as a recruiter or admin user. Grant the connector access to the roles or departments you want Claude to see (not your whole ATS unless needed).
5. Test: “Show me the five most recent applicants for the [role name] role.” If they come back, Workable is live.

Indeed, ZipRecruiter, and Dice use OAuth via their respective developer programs. Metaview uses an API key generated in its admin panel. Visier and Carta require enterprise OAuth with admin approval; expect a short setup conversation with whoever owns your Visier or Carta account.

What are the limits?

• Candidate write actions are conservative. Posting jobs, moving candidates through stages, sending offers all require explicit write scope. Default is read-only.
• PII volume. Applicant records contain PII. Claude reads them per-request, processes them, does not retain on Anthropic servers for paid plans, but you should still treat the workflow as you would any third-party HRIS access.
• Metaview transcripts are per-interview. Cross-interview analysis (calibration, interviewer comparison) requires you to pull each transcript and reference them in the prompt explicitly.
• Visier and Carta require enterprise seats. These are paid platforms with strict per-seat licensing. The connector consumes your admin seat’s API quota.

Are these connectors safe to use with work data?

HR data is one of the most-regulated data categories. For paid Claude plans the safeguards:

• Restrict ATS connector scope to the roles or departments you specifically need Claude to see. Workable, Greenhouse, and Lever all support per-role scoping; use it.
• EEO data, salary data, and protected-class information should be handled with the same care your HRIS already enforces. Do not bypass scope just because Claude makes it convenient.
• Interview transcripts may contain sensitive disclosures by candidates. Have your legal team review the Anthropic data-processing terms for HR-specific workflows before broadly adopting Metaview integration.
• For comp decisions involving Carta data, treat Claude as you would any other reviewer; the actual decision and the documentation remain yours.
• Enterprise admins can restrict HR connector access at the Claude Team or Enterprise level.

When does a connector pay off vs. just chatting with Claude?

Connectors earn their setup time when the data updates faster than you can retype it, lives behind login, or runs into the thousands of items. For one-off questions about static information, plain Claude through the chat interface is faster than installing anything. The break-even is usually around the third time you would otherwise be copy-pasting context for the same kind of question. For the full list of connectors and which pillar each belongs to, see the Claude Connectors hub. If a term in this post is unfamiliar, the AI Glossary has plain-English definitions.

Frequently asked questions

Can Claude make hiring decisions?

No, and you should not let it. Claude can rank, draft, summarize, and surface signals. The hire/no-hire call should always be a human with accountability. Treating Claude output as the decision creates EEO and discrimination risk.

Will the Workable connector send rejection emails automatically?

Only with explicit write scope, which you should not grant for high-volume rejection. Have Claude draft them; you review and send. This stops a misclassification from sending a rejection to a strong candidate.

Can Claude detect bias in my interview feedback?

It can surface patterns: which interviewer consistently rates candidates from a certain background lower, which questions tend to filter out specific cohorts. But the interpretation needs a human with EEO context.

Does the Carta connector show me employee equity individually?

Yes, with the same access scope your Carta role allows. Treat the data accordingly; restrict to specific scenarios rather than broad sweeps.

Can Claude write offer letters?

Drafts, yes. Legal review and signature stay with you. For high-volume hiring, build a template flow where Claude fills in role-specific variables and HR ops reviews before sending.

Does Metaview record interviews automatically?

Metaview handles recording and transcription in its own UI. The connector exposes the resulting transcripts to Claude. You configure the recording behavior inside Metaview before the interview, not via Claude.

Sources

• Anthropic: Introducing Connectors · official launch and partner list
• Workable API documentation · Workable connector scope
• Metaview developer docs · interview transcript scope
• Visier developer docs · people analytics connector reference
• Anthropic Trust Center · privacy posture for HR data

You might also like

• Claude Connectors Guide (2026) · the master hub
• Claude Connectors for Finance + Accounting · Carta overlap for comp decisions
• Claude Connectors for Email + Productivity · the daily-driver sibling
• Best Claude Prompts for Performance Reviews · manager workflows
• Best AI Prompts for Job Interviews · the candidate-side companion
• How to Use Claude AI · the beginner walkthrough
• Best Claude Prompts: 50 Examples · the broader collection
• Best AI Prompts by Job and Use Case · 60+ prompt packs organized by role and artifact