Overview
Miki integrates with Greenhouse in two directions, giving you a complete assessment workflow:
← Assessments (UC1)
Greenhouse sends candidates to Miki for assessment. Results flow back automatically — scores, trait breakdowns, and full reports appear directly in Greenhouse.
→ Candidate Push (UC2)
Push qualified candidates from Miki into Greenhouse with scores, scorecards, and stage placement. Manual or automatic triggers.
You can use UC1 and UC2 independently or together. They use different API credentials and don't interfere with each other.
Quick Start: Assessment Partner (UC1)
Set up Greenhouse to send candidates to Miki for automated sales assessments.
Enable the integration
Go to Settings → Integrations → Greenhouse → Assessments tab. Toggle Enable Assessments to ON.
Copy your Partner API Key
Your unique key appears after enabling. Copy it to your clipboard.
Configure in Greenhouse
Give your Partner API Key to your Greenhouse Account Manager. They'll add Miki as an Assessment Partner. Alternatively, configure it yourself under Settings → Dev Center → Assessment Partners.
Add Miki to job hiring plans
In Greenhouse, go to a Job → Hiring Plan → Interview Plan. Add a "Miki Assessment" stage. Choose which Miki scenario to use.
View results
When a candidate completes their assessment, scores and the full report appear in Greenhouse. Filter and sort candidates by Miki score.
Quick Start: Candidate Push (UC2)
Push assessed candidates from Miki into Greenhouse with scores, scorecards, and PDFs.
Connect your Harvest API key
Go to Settings → Integrations → Greenhouse → Candidate Push. Enter your Greenhouse Harvest API key (found in Greenhouse → Configure → Dev Center → API Credential Management).
Select an acting user
Choose which Greenhouse user Miki should act as when pushing candidates. This user needs Job Admin permissions.
Map your jobs
Map each Miki job to a Greenhouse position and (optionally) a specific hiring stage.
Configure scorecard thresholds
Set how Miki scores translate to Greenhouse recommendations (Strong Yes / Yes / Mixed / No / Definitely Not).
Push candidates
Click the Push to Greenhouse button on any completed assessment. Or configure auto-push triggers (see below).
Auto-Push Triggers
Configure automatic pushing in the Push Triggers section:
- Manual only — push via button only (default)
- On assessment complete — auto-push every completed assessment
- On score threshold — auto-push when score ≥ your configured minimum
Auto-push does NOT retry on failure to avoid creating duplicate candidates. Check the sync dashboard for failures and retry manually.
Bidirectional Sync
Enable webhook sync to receive real-time status updates from Greenhouse when candidates move stages, get hired, or are rejected.
Enable webhook sync
In the Bidirectional Sync section of the Candidate Push tab, toggle Enable webhook sync.
Copy the webhook URL
Click the copy button next to the webhook URL shown.
Configure in Greenhouse
In Greenhouse, go to Configure → Dev Center → Webhooks. Create a new webhook with the URL from step 2. Enter a shared secret and copy it into Miki.
Subscribe to events
Subscribe to: Candidate Rejected, Candidate Hired, Candidate Stage Change.
What syncs
| Greenhouse Event | Miki Action |
|---|---|
| Candidate rejected | Marks assessment as rejected, stops active assessments |
| Candidate hired | Marks assessment as hired |
| Stage change | Logged to sync activity (informational) |
Only candidates originally pushed from Miki are affected by inbound webhooks. Candidates that were never in Miki are ignored.
Scorecard Mapping
When Miki pushes a candidate to Greenhouse, it creates a scorecard with an overall recommendation based on the assessment score.
| Miki Score | GH Recommendation | Default Range |
|---|---|---|
| Strong Yes | definitely_yes | 80–100 |
| Yes | yes | 60–79 |
| Mixed | mixed | 40–59 |
| No | no | 20–39 |
| Definitely Not | definitely_not | 0–19 |
Customize these thresholds in the Scorecard Mapping section of the Candidate Push tab. Use the live preview to test how scores map to recommendations.
Trait Attributes
Each scorecard includes individual trait scores (Messaging Adherence, Discovery & Diagnosis, Objection Handling, etc.) as Skills-type attributes. These appear in the Greenhouse scorecard alongside the overall recommendation.
Troubleshooting
FAQ
API Reference
Technical reference for the endpoints Miki exposes and consumes.
UC1 Endpoints (Assessment Partner)
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/greenhouse/list-tests | List available scenarios for Greenhouse |
| POST | /api/greenhouse/send-test | Receive a test request from Greenhouse |
| GET | /api/greenhouse/test-status | Poll assessment status |
| GET | /api/greenhouse/report/:id | Fetch signed report link |
UC2 Endpoints (Candidate Push)
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/integrations/greenhouse/push/:id | Push assessment to Greenhouse |
| GET | /api/integrations/greenhouse/sync-log | List sync activity (paginated) |
| POST | /api/integrations/greenhouse/sync-log/:id/retry | Retry a failed push |
| GET | /api/integrations/greenhouse/health | Integration health status |
Webhook Events We Handle
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/webhooks/greenhouse | Receives all Greenhouse webhook events |
Supported event types: candidate_rejected, candidate_hired, candidate_stage_change, application_updated.
Need Help?
Contact us at support@meetmiki.com or reach out through the chat widget in your Miki dashboard.