Recruiting & ATS · Integration
Greenhouse
Add Greenhouse to your product for your customers, and give your AI agents governed access to it.
Embed a Greenhouse integration so your customers can work their own hiring pipeline from inside your product. Recruiting data is sensitive and its access rules are stricter than most systems, so access is scoped per tenant, limited to the fields you map, and every read and write is logged. fastn handles per-customer authentication, pagination over large candidate lists, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their open jobs and the candidates at each stage into your product.
Create a candidate or an application from your product so sourcing does not need a second tool.
Read interviews and scorecards so your product can report on hiring progress.
Trigger your product when a candidate changes stage or an offer is accepted, so onboarding starts on time.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises where each candidate sits in a pipeline before a hiring meeting.
An agent advances or rejects a candidate within governed permissions, with each action audited.
An agent reacts to an accepted offer and starts provisioning across the customer's other systems.
Example prompt
List candidates at onsite stage for this role and flag anyone waiting more than five days on a scorecard.
Set up Greenhouse in 4 steps
- 01Open the Greenhouse connector from your fastn dashboard.
- 02Have each customer authenticate their own Greenhouse account.
- 03Map the jobs, candidate fields, and stages your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Greenhouse integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Greenhouse integration without building it. Your customers connect their own Greenhouse account inside your product and work their job requisitions, candidates and applications there, with no per-customer code on your side.
- Handle the part that actually costs time: candidate records are personal data with consent and retention rules attached. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Greenhouse update is not your on-call problem.
- One integration serves your product and your agents. The same governed Greenhouse connection powers in-product features and gives AI agents scoped, audited access, so you keep hiring pipelines moving without manual re-entry without wiring it twice.
Used by these teams
Works well with
Workday
BambooHR
GustoOften used alongside
Tools the same teams tend to run next to Greenhouse, across other categories.
Slack
Notion
Box
DocusignGreenhouse integration FAQ
How do I add a Greenhouse integration to my product?
Enable the Greenhouse connector in your fastn dashboard, then let each customer authenticate their own Greenhouse account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Greenhouse client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Greenhouse account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Greenhouse account and only ever sees their own job requisitions, candidates and applications. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Greenhouse integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises where each candidate sits in a pipeline before a hiring meeting.
Who maintains the Greenhouse integration?
fastn does. When Greenhouse changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How is candidate data from Greenhouse handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. That matters more here than in most systems, because candidate records are personal data that carry consent and retention obligations.
Can my product react when a candidate's status changes in Greenhouse?
Yes, through event triggers: a stage move where Greenhouse owns the pipeline, or a completed assessment, a returned report or a finished reference where it owns one step in it. Events are delivered per tenant and can be replayed after an outage, so a hiring team does not silently lose an update while your product was unreachable.
What can I build with the Greenhouse integration?
A common starting point: read their open jobs and the candidates at each stage into your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Greenhouse integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Greenhouse does not change your per-connector cost. You can start free with 3 connected accounts.
Add Greenhouse to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.