Skip to main content
This guide walks through a manual integration between Promptster and Greenhouse. You will create assessments via the Promptster API, store candidate keys in Greenhouse custom fields, and write results back to Greenhouse scorecards.
A native Greenhouse integration is on the roadmap. This guide covers the API-based approach for teams that want to integrate now.

Prerequisites

  • A Promptster org API key with read and write scopes
  • A Greenhouse API key with candidate and scorecard permissions
  • A custom field in Greenhouse for storing the Promptster candidate key

1. Set up Greenhouse custom fields

In Greenhouse, create two custom candidate fields:
  • Promptster Key (text) — stores the PST-XXXX-XXXX candidate key
  • Promptster Session ID (text) — stores the session ID after redemption

2. Create a Promptster assessment for each job

When you open a new role in Greenhouse, create a matching Promptster assessment:
Store the assessment ID in your integration config, mapped to the Greenhouse job ID.

3. Generate keys when candidates reach the assessment stage

When a candidate moves to the “Technical Assessment” stage in Greenhouse, generate a Promptster key and store it on their profile:

4. Poll for results

Run a periodic job (every 5 minutes) to check for completed sessions:

5. Write Greenhouse scorecards

Submit scores to Greenhouse using their scorecard API:
Store the Promptster session URL in the scorecard notes so reviewers can click through to the full replay view.

Automation options

For a fully automated pipeline, consider:
  • Greenhouse webhooks: Listen for candidate_stage_change events to trigger key generation
  • Cron job: Poll Promptster every 5 minutes for newly completed sessions
  • Zapier/n8n: Use HTTP request steps to connect the two APIs without custom code
Rate limits apply to both APIs. The Promptster API allows 300 requests per minute. Greenhouse’s Harvest API has its own rate limits — check their documentation.