You've found a sales assessment tool that works. Your VP Sales is excited. Your Head of Recruiting has one question: "Does it integrate with Greenhouse?"
This question will determine whether the tool actually gets used or quietly becomes another abandoned subscription. Assessment tools that live outside the recruiting workflow don't survive. The recruiter forgets to send the link. The scores live in a separate tab. The hiring manager never sees the results because they live in Greenhouse all day, not in your-cool-new-assessment-tool.com.
Here's everything you need to know about connecting assessment tools to your ATS — and the questions that separate real integrations from marketing claims.
Why Integration Makes or Breaks Adoption
The best assessment tool in the world is useless if nobody remembers to use it.
Manual process without integration:
- Candidate reaches assessment stage in ATS
- Recruiter copies candidate email from ATS
- Recruiter logs into assessment tool
- Recruiter creates assessment, enters candidate info, sends link
- Candidate completes assessment
- Recruiter logs into assessment tool (again), finds results
- Recruiter copies score and recommendation
- Recruiter pastes into ATS notes
- Hiring manager reads notes (maybe)
That's 9 steps, 2 different logins, and at least 3 copy-paste operations per candidate. Multiply by 30 candidates per role and the recruiter stops at step 3.
Integrated process:
- Candidate reaches "Assessment" stage in ATS → assessment link sent automatically
- Candidate completes assessment → score, recommendation, and transcript appear in ATS
- Hiring manager sees results in the candidate's ATS profile
Three steps. Zero copy-paste. Zero separate logins. The assessment is part of the workflow, not a separate task.
The difference in adoption is the difference between the tool being used on 100% of candidates and being used on the first 5 before the recruiter gives up.
Integration Types: What You're Actually Getting
Not all "integrations" are equal. When a vendor says "we integrate with your ATS," ask: which kind?
Native Integration
What it means: Built-in connection between the assessment tool and the ATS, using the ATS's official partner API. One-click setup, bi-directional data flow, maintained by both teams.
What it looks like in practice:
- Assessment appears as a stage action in the ATS
- Candidate moves to "Assessment" stage → assessment invitation triggers automatically
- Scores, transcripts, and recommendations push back to the candidate's ATS scorecard
- Hiring manager never leaves the ATS
Pros: Best user experience. Most reliable. Maintained by both vendors. Usually includes the ATS's compliance and data-handling standards.
Cons: Only available for major ATSs. A vendor saying "native integration" usually means they've built it for 1–3 ATSs, not all of them.
Red flag to watch for: "Native integration" that requires API keys, custom configuration, or engineering time. True native integrations are setup-wizard-level simple.
Webhooks
What it means: Event-based triggers. When something happens in the assessment tool (candidate completes, score generated), a data payload is sent to a URL you specify. Most modern ATSs support incoming webhooks.
What it looks like in practice:
- Assessment completion triggers a webhook
- Webhook sends score, recommendation, and candidate ID to the ATS
- ATS receives data and attaches it to the candidate profile
- May require some configuration on the ATS side
Pros: Works with any ATS that supports webhooks (which is most of them). Flexible — you control what data goes where. Faster to set up than a custom API integration.
Cons: Typically one-directional (assessment → ATS, not ATS → assessment). Auto-triggering the assessment from the ATS may require additional setup. Less polished UX than native.
Best for: Teams using ATSs without native integration support. Lever, Ashby, BambooHR, Workday, and dozens of others support inbound webhooks.
API
What it means: Full programmatic access to the assessment tool's data and functions. Your engineering team builds whatever integration you need.
What it looks like in practice:
- Anything you want — fully custom
- Requires engineering time to build and maintain
- Maximum flexibility, maximum effort
Pros: Complete control. Can build complex workflows (auto-trigger assessments, custom scoring displays, internal dashboards that combine ATS + assessment data).
Cons: Requires engineering resources. You maintain it. If the API changes, you update your integration. For most mid-market teams, this is overkill.
Best for: Large organizations with dedicated recruiting ops engineers, or teams with highly custom ATS/hiring workflows.
Middleware (Zapier/Make)
What it means: Using a third-party automation tool to connect the assessment tool to the ATS.
Honest assessment: This works for prototyping but is fragile in production. Zapier steps break when APIs change. Make scenarios require monitoring. Authentication tokens expire. For a process that handles candidate data and hiring decisions, middleware isn't reliable enough.
Best for: Proving the concept before committing to a real integration. Not recommended for production use.
What Good ATS Integration Actually Looks Like
When you're evaluating assessment vendors, this is the standard:
Trigger: Candidate enters "Assessment" pipeline stage in ATS → assessment invitation sent automatically (email to candidate with assessment link).
During: Candidate completes assessment at their own pace. No action required from recruiter.
Completion: Assessment results — overall score, dimension scores, hiring recommendation, transcript link — are automatically posted to the candidate's ATS profile/scorecard.
Review: Hiring manager opens candidate in ATS, sees assessment results alongside resume, interview notes, and other data. Makes decision with complete picture.
Edge cases handled:
- Candidate doesn't complete assessment → status shows "Incomplete" in ATS, not blank
- Multiple assessment types (chat + voice) → both results appear, clearly labeled
- Candidate retakes assessment → latest result shown, previous results archived
If the vendor can't describe this workflow for your specific ATS, the "integration" is probably a webhook that requires your team to build the plumbing.
Miki's Integration Approach
Greenhouse: Native integration. Miki is a Greenhouse Assessment Partner. One-click setup in Greenhouse settings. Candidate enters assessment stage → Miki link sent automatically → scores and transcripts posted back to Greenhouse scorecard. Setup time: 10 minutes.
Webhooks: Available on all plans. Works with Lever, Ashby, BambooHR, Workday, or any ATS that supports inbound webhooks. Configure the webhook URL in Miki's settings. Assessment completion triggers a payload with candidate ID, overall score, dimension scores, recommendation, and transcript link.
API: Available on Scale plan. Full REST API for custom integrations. Documentation at meetmiki.com/api. Use cases: custom internal dashboards, automated pipeline management, multi-tool hiring workflows.
Five Questions to Ask Any Assessment Vendor About ATS Integration
Before you buy, ask:
1. "Is this a native integration or webhooks?" "We integrate with Greenhouse" could mean native partner API integration or "we can send a webhook." The experience difference is significant. Ask specifically.
2. "Does the score automatically appear in the candidate's ATS profile?" If the answer involves "export" or "download" or "copy the link," it's not a real integration.
3. "Can the assessment trigger automatically from a pipeline stage?" If recruiters have to manually send assessment links, adoption will drop. The trigger should be automatic when a candidate enters the right stage.
4. "What happens if the candidate doesn't complete the assessment?" Good integrations surface "Incomplete" status. Bad integrations show nothing — and the recruiter doesn't know if the candidate was sent the assessment, hasn't started it, or started and abandoned it.
5. "How long does setup take? Do I need engineering?" Native integrations: 10–30 minutes, no engineering. Webhooks: 1–2 hours with recruiter ops. API: days to weeks with engineering. Match the setup complexity to your team's resources.
The Integration That Matters Most
Here's a truth most vendors won't tell you: the ATS integration matters more than the assessment itself for adoption.
A mediocre assessment with great ATS integration will get used on every candidate. A brilliant assessment with no integration will get used on the first 10 before the recruiter gives up on the manual process.
When evaluating tools, check the integration first. If it doesn't fit cleanly into your recruiting workflow, the quality of the assessment is academic.
See how Miki integrates with your ATS. Greenhouse native, webhooks for everything else.