Teamable is a recruiting CRM and candidate-sourcing platform. Teamable's integration with Greenhouse Recruiting allows users to source and engage candidates in Teamable and keep them in sync with Greenhouse Recruiting — pushing new candidates and prospects, outreach activity, stage changes, tags, and dispositions into Greenhouse, while reading jobs, candidates, stages, and configuration back out of Greenhouse so recruiters work from one consistent set of data.
Configure the Teamable integration
The integration authenticates with Greenhouse using partner OAuth 2.0 (authorization code flow). You authorize Teamable's Greenhouse app once; Teamable then stores a per-account token (refreshed automatically) and no API key is copied or stored manually.
Before you begin
- You must be a Site Admin in Greenhouse (the permission level Greenhouse requires to authorize a Harvest v3 partner integration).
- Authorizing with a service account is recommended. Harvest v3 attributes the authorization to the Greenhouse user who grants it, so on the authorization screen — after you enter your email — check "Authorize using a service account". Greenhouse then creates an org-level service account to own the authorization, so the connection isn't tied to your personal Greenhouse user. See Greenhouse's guide: Connect to Harvest v3 partner integrations.
- Your Teamable account must be configured as a team admin.
Steps
Sign in to Teamable at app.teamable.com, click your name in the left sidebar to open the account menu, choose Account, then open Integrations and click Connect Greenhouse.
You're redirected to Greenhouse's authorization screen. The integration is listed in Greenhouse as Teamable (its registered app name) — this is expected; it's the same Teamable integration. Enter your email, review the permissions being requested, and — recommended — check "Authorize using a service account" so the connection is owned by an org-level service account rather than your personal Greenhouse user.
Click Authorize. Greenhouse redirects you back to Teamable (app.teamable.com/ats/greenhouse/oauth/callback).
Teamable shows Connected via OAuth and begins syncing your Greenhouse jobs, candidates, and configuration automatically. Finish setup on this same screen: pick the Stages that describe your hiring process, and under Selections for Outbound Jobs choose the Candidate first stage (where sourced candidates land when outreach is sent). (When you source someone they're added to Greenhouse as a prospect; when they show interest they become a candidate.)
To disconnect, return to the same settings screen and click Disconnect Greenhouse.
Data Teamable reads from Greenhouse
Teamable reads the following to build a recruiter's working view (candidates, jobs, and the dropdowns used across the app):
| Greenhouse resource | Used in Teamable for |
| Candidates | The candidate record (name, emails, phone, company, title, links) |
| Applications | The candidate's job + current stage, status, source, applied date |
| Attachments | The candidate's résumé |
| Candidate tags / applied tags | Tags shown on a candidate and the tag picker |
| Jobs | The jobs list |
| Job posts | The job's posting — posting title, job description, and whether the posting is live. |
| Departments | Department shown on a job |
| Offices | Job office/location (also seeds location-based sourcing) |
| Job hiring managers / job owners | The job's hiring team → "my jobs" filtering and the job's primary recruiter (which seeds the default inbound reviewer) |
| Interview stages | The job's stage definitions — populate stage dropdowns and the pipeline a candidate moves through. (Stage definitions only — Teamable does not read interviews, scorecards, or feedback.) |
| Users | Recruiter / owner names |
| Sources | Candidate source (badge + filter) and source attribution on push |
| Prospect pools | Indicate the pool when pushing prospects |
| Rejection reasons | The reason dropdown when rejecting |
| Email templates | Shown in the rejection-email template dropdown. Teamable optionally uses them when rejecting inbound applicants. |
Data Teamable writes to Greenhouse
When a recruiter acts in Teamable, the following is written back to Greenhouse:
| Action in Teamable | What's created/updated in Greenhouse |
| Source / add a candidate to a job | Creates the candidate — name, company, title, email, LinkedIn & personal URLs, tags, source — and an application on the job, as a prospect in the selected prospect pool. |
| Attach a résumé | Adds the candidate's résumé to the application — when the candidate has a résumé on file (skipped otherwise). |
| Log outreach activity | Adds notes, and logs sent emails, on the candidate's Greenhouse timeline. |
| Advance a candidate | Moves the application to the next interview stage (from the jobs-tab stage actions). |
| Reject a candidate | Rejects the application with a rejection reason and a rejection email. |
| Convert a prospect → candidate | Converts a prospect to a candidate when they show interest. |
| Add / remove a tag | Creates and applies tags, and removes tags you remove in Teamable. |
Use the Teamable integration
Once connected, recruiters work in Teamable and Greenhouse stays in sync. The most common workflows:
Source a candidate from Teamable to Greenhouse
- Find a candidate in Teamable or using the Chrome extension and add them to a Greenhouse-synced job.
- Run outreach — Teamable sends the email and logs it back to the candidate's Greenhouse timeline.
- The candidate now appears in Greenhouse on that job (as a prospect, with Teamable as a source and a copy of messaging).
Convert a prospect to a candidate
When you source someone into Greenhouse, they're added as a prospect. When that person shows interest, Teamable converts them into a candidate at your configured Candidate first stage, so an interested person enters the active pipeline automatically.
Tag a candidate
When you add or remove a tag on a candidate in Teamable, the change is pushed to that candidate in Greenhouse — added tags are applied, and tags you remove in Teamable are removed in Greenhouse.
Additional resources
For help with the Teamable Greenhouse integration, contact support@humanly.io.
FAQ / notes
- Why should I authorize with a service account? Harvest v3 attributes synced actions to the authorizing Greenhouse user; a service account keeps that activity under a dedicated org-level account rather than an individual's. See the Greenhouse guide linked above.
- What happens if the connection expires? Teamable refreshes access automatically; if the account is disconnected, reconnect from the same settings screen to restore syncing.