Obra is a recruiting technology company operating a two-sided hiring platform. Obra Hire is a sourcing product that lets recruiters and hiring managers search a database of hundreds of millions of candidate profiles using natural-language queries or structured filters, then manage the candidates they find through a project-based pipeline. Obra Jobs is the companion job seeker product, where candidates receive job recommendations, track their applications, and get AI-assisted career guidance.
Obra's integration with Greenhouse Recruiting allows users to enrich Obra Hire candidate search with the people already in their Greenhouse account, build searches directly from their live Greenhouse job descriptions, and publish selected Greenhouse job posts to Obra Jobs to drive additional applicant flow.
Configure the Obra integration
Prerequisites
Before you begin, confirm the following:
- Your Obra workspace is on the Scale or Enterprise plan. ATS integrations are not available on the Free or Explore tiers.
- You are an Admin of the Obra team you want to connect. Members cannot configure integrations.
- You have Greenhouse Recruiting credentials with sufficient permissions to authorize a third-party application on behalf of your organization.
Note: One Greenhouse account connects to one Obra team. If your organization uses multiple Obra teams, repeat these steps in each team you want to connect.
Open the integrations directory in Obra
Sign in to Obra at app.obra.co and select Settings from the left sidebar, then select Integrations.
Locate Greenhouse
Use the Search for integration field at the top of the page to find Greenhouse, then select Connect on the Greenhouse card.
Authorize the connection
Selecting Connect opens a secure authorization window.
Follow the prompts in the window to sign in to Greenhouse Recruiting and grant access.
Confirm the connection
When authorization completes, the window closes and you are returned to the Obra integrations directory. The Greenhouse card now shows a connected state.
Obra begins an initial sync of your Greenhouse data immediately. After the initial sync, Obra stays current using Greenhouse webhooks, so changes in Greenhouse are reflected in Obra shortly after they occur.
Data accessed by this integration
The authorization screen lists the full set of permissions Obra's Greenhouse connector requests. Obra currently reads the objects listed below and does not create, update, or delete records in your Greenhouse account. Write functionality is planned; this article will be updated when it ships.
Obra reads the following objects through the Greenhouse Harvest API:
| Greenhouse object | What Obra uses it for |
| Jobs | Every position your organization is hiring for. Powers search-by-job-description in Obra Hire. |
| Job Posts | The published versions of a job across your internal career page, external career page, and job boards. These are the postings you can choose to publish to Obra Jobs. |
| Job Stages | The steps an application moves through before hire. Used to interpret where an application currently sits. |
| Applications | The link between a candidate and a job they applied to, including the stage the application is in. |
| Candidates | People who applied through Greenhouse or were added to it manually. Used to enrich Obra Hire search results. |
Field mapping
| Greenhouse | Obra |
| Job id | Greenhouse job ID on raw.remote_id. Hire job ID and internalId are the Kombo job ID. |
| Job name | Job title |
| Job status | Job status. OPEN maps to Published. Anything else maps to Delisted. |
| Job departments | Not mapped. Kept on raw.department only. |
| Job offices / location | Job location (city, state, country) |
| Job description (Kombo description) | Job description, HTML and plain text |
| Job employment type | Job type |
| Job salary range, currency, period | Compensation |
| Job remote work status | Workplace (remote, hybrid, onsite) |
| Job experience level | Seniority |
| Job post_url | Application URL |
| Job created_at / opened_at | Job date and start date |
| Job closed_at | End date and delisted date |
| Job Post id | Not imported as an Obra object |
| Job Post title | Not mapped. Hire uses Job name. |
| Job Post content | Not mapped as its own field. Hire uses Job description. |
| Job Post location | Not mapped. Hire uses Job location. |
| Job Post live, internal, external | Not mapped. OPEN jobs are imported. Visibility does not publish to Obra Jobs. |
| Job Stage id | Not mapped onto an Obra stage catalog |
| Job Stage name | Current application stage name |
| Job Stage priority | Not mapped |
| Application id | Greenhouse application ID on raw.remote_id. Hire application ID is the Kombo ID. |
| Application candidate_id, job_id | Candidate-to-job relationship |
| Application current stage | Current stage name only |
| Application Harvest status | Not mapped. Obra stores Kombo outcome (PENDING, HIRED, DECLINED). |
| Application created_at | Application created date |
| Application rejection reason | Rejection reason |
| Application Greenhouse URL | Link to the application in Greenhouse |
| Candidate id | Greenhouse candidate ID on raw.remote_id. Hire candidate ID is the Kombo ID. |
| Candidate first_name, last_name | Candidate name |
| Candidate email_addresses | Primary email (WORK preferred) |
| Candidate phone_numbers | Primary phone (WORK preferred) |
| Candidate company | Current company |
| Candidate title | Current title |
| Candidate source | Candidate source |
| Candidate location | Candidate location |
| Candidate tags | Candidate tags |
| Candidate social profiles | LinkedIn URL and social links |
| Candidate confidential | Confidential flag |
| Candidate Greenhouse URL | Link to the candidate in Greenhouse |
| Candidate employments | Not imported |
| Candidate educations | Not imported |
Use the Obra integration
Search your Greenhouse candidates alongside Obra's database
Once connected, candidates from your Greenhouse account are compared against all candidates within Obra Hire and will highlight candidates that already exist in their Greenhouse instance. There is no separate view to check. A search for "Software Engineers in Chicago with 5+ years of experience" returns results making it easy to identify candidates you already have in your ATS along with a simple link to open directly to their profile in the ATS.
This surfaces qualified people who already applied to your organization and would otherwise sit unreviewed in your ATS.
To run a search:
- Select Search from the Obra sidebar.
- Describe the role in the Job Description field, or select Filter Search to build criteria by hand.
- Review the parsed criteria, then select Confirm Search.
Build a search from a live Greenhouse job
Rather than describing a role from scratch, you can start a search from a job that already exists in Greenhouse. Obra reads your active job descriptions and converts the selected one into search criteria — job titles, location, and must-have and nice-to-have filters — which you can review and adjust before running.
Publish Greenhouse job posts to Obra Jobs
Obra Jobs is Obra's job seeker product. Publishing your Greenhouse job posts there exposes them to Obra's job seeker audience and drives additional applicants to your Greenhouse pipeline.
Publishing is opt-in per posting. Your Greenhouse job posts sync into Obra, and an Admin selects which ones to publish. Nothing is published to Obra Jobs automatically.
- Go to the Edit Jobs link in the integrations menu under the Active Greenhouse integration.
- Review the list of job posts synced from Greenhouse.
- Select the postings you want to make visible on Obra Jobs.
- Save your selection.
Postings that are closed or unpublished in Greenhouse are removed from Obra Jobs. To stop a posting from appearing on Obra Jobs without changing it in Greenhouse, deselect it on this screen.
Disconnect the integration
To end the connection, go to Settings > Integrations > Locate Greenhouse > Triple Dot > Disconnect ATS. Following this the integration will be disconnected.
Additional resources
For additional information not covered here, reach out to product@obra.co.
Frequently asked questions
Does Obra write anything back to Greenhouse? No. This integration is read-only. Obra does not create, edit, or delete jobs, candidates, or applications in your Greenhouse account. Write functionality is planned; this article will be updated when it ships.
How current is the data in Obra? Obra uses Greenhouse webhooks wherever they are available, so changes in Greenhouse are reflected in Obra shortly after they occur.
Do Greenhouse-sourced candidates consume Obra contact credits? The Obra user has the option to click the In-ATS badge which will navigate them directly to the candidate's profile within their ATS. However, they will still have the option to reveal contact information within Obra Hire to potentially expose additional methods of available contact information, or more recent contact information, for the candidate that they may not have in their ATS.
Which Obra plans include this integration? ATS integrations are currently available on the Scale and Enterprise plans.