Greenhouse

Connect Greenhouse and your assistant can work with your recruiting data — candidates, applications, jobs, interviews, scorecards, and offers — so hiring workflows like interview prep, pipeline reviews, and candidate research happen without leaving Town.

Everything runs as you: your Greenhouse account’s access is the ceiling — your assistant can never see or do more than you can, and it works with the specific data listed in the capability table below. Changes that can reach a candidate — a stage move, a rejection, an interview record — ask for your approval before they happen, and in routines you trust, you can let Greenhouse updates run automatically.

What’s included

With Greenhouse connected, your assistant can:

Search and read recruiting data — jobs, interview stages and the interviews in each, candidates, applications, scorecards, offers, scheduled interviews, users, and rejection reasons
Move candidates through your pipeline (with approval) — advance applications between stages, reject, or un-reject
Add notes — leave internal notes on a candidate’s profile
Keep interview records up to date (with approval) — create, update, or remove the record of a scheduled interview in Greenhouse
Update records — edit candidate details and job basics

Connecting Greenhouse

Greenhouse is in a limited beta. If you don’t see Greenhouse on your Integrations page, it hasn’t been enabled for your account yet — reach out through Get Help in the app to request access.

Connect with a Site Admin account. Greenhouse’s API returns data only for Site Admin users, so Town checks this during connect — a non-admin account can’t complete the connection. If you’re not a Site Admin, ask your Greenhouse admin to upgrade your access before connecting.

Go to Integrations
Find Greenhouse and click Add account, keep or edit the label, then click Continue
Sign in to Greenhouse (as a Site Admin) and authorize Town when prompted
Return to Town

For the Greenhouse-side walkthrough, see Greenhouse’s own guide: Town integration .

Town connects through Greenhouse’s official partner OAuth — no API keys or setup. Your assistant is limited to what your Greenhouse account can already see and do, and you can disconnect anytime from Town’s Integrations page.

What your assistant can do

Capability	What it does	Makes changes?
List jobs and stages	Browse open roles, their interview stages, and the interviews in each stage	No
Look up candidates	Find a candidate by email, or list recently updated candidates, and read their profile basics — contact details, company, title, and tags	No
List applications	See where candidates sit in each pipeline, filtered by job or status	No
Read scorecards	Review submitted interview feedback and ratings	No
Read offers	See offer status, send dates, and start dates	No
List scheduled interviews	See upcoming and past interviews	No
Look up users and rejection reasons	Find interviewer IDs and your org’s configured rejection reasons	No
Move an application	Advance an application to the next stage, or a specific one	Yes (with approval)
Reject or un-reject an application	Mark an application rejected, or restore it	Yes (approval to reject)
Add a note	Leave an internal note on a candidate	Yes
Record a scheduled interview	Create, update, or remove an interview record in Greenhouse	Yes (with approval)
Update a candidate	Edit candidate record details	Yes
Update a job	Edit job basics	Yes

Changes that can reach a candidate — stage moves, rejections, and interview records — ask for your approval first. Internal record edits (notes, candidate and job details) apply directly, and are reversible in Greenhouse. In routines you trust, you can allow any of these actions to run automatically — or set any action to Always ask.

Interview tools update Greenhouse records only. Recording, updating, or removing a scheduled interview changes what Greenhouse shows — it does not send calendar invites, reschedule notices, or emails to candidates or interviewers. Use your calendar for the actual invite.

Use cases

Interview prep

“Prep me for my 10am interview — pull the candidate’s profile, application history, and the scorecards submitted so far.”
Combine Greenhouse interview context with your calendar and meeting notes

Pipeline reviews

“Summarize where every candidate stands for the Senior Product Manager role.”
“Show me every active application for this role, grouped by stage.”

Keeping Greenhouse up to date

After a debrief, advance a candidate to the next stage (you approve the move)
Add an internal note capturing a hiring-team decision
Record an interview you scheduled over email so the pipeline reflects reality

Example routine


Every weekday at 8am:
1. Check my calendar for today's interviews
2. For each, look up the candidate in Greenhouse and pull their application and prior scorecards
3. Send me a prep brief before the first interview

Good to know

Not a sync integration. Town reads your Greenhouse data on demand when you ask — there’s no background sync and no replicated copy of your Greenhouse database. Like any integration, what your assistant retrieves does appear in that conversation’s history.
Town never supplies rejection emails or creates jobs. Neither is in the tool set.
Stage moves and rejections can trigger your Greenhouse automations. If your org has configured emails or actions on stage transitions or rejections, a change your assistant makes (after your approval) can fire them — the same as the change made in Greenhouse directly.
Recruiting data is sensitive. In routines, choose deliberately which Greenhouse actions run automatically and which keep asking (any action can be set to Always ask), and scope routines to the roles you own.
Access can be revoked on the Greenhouse side. If your Greenhouse admin revokes Town’s access or deactivates your account, the connection stops working — reconnect from the Integrations page once access is restored.
Your access is the ceiling, not the floor. The assistant can never see or do more than your Greenhouse account allows, and it works with the specific data in the capability table above — some Greenhouse data (for example, scorecard question-level answers) isn’t part of the integration. If something seems missing, check the table first, then your Greenhouse permissions.

Troubleshooting

Searches return nothing

Confirm the connected account is still a Greenhouse Site Admin — if your role was downgraded after connecting, Greenhouse returns empty results rather than errors
If Town shows Greenhouse as disconnected (for example, after access was revoked in Greenhouse), reconnect from the Integrations page

Can’t connect

If you see a message about Site Admin access, the account you signed in with isn’t a Greenhouse Site Admin — ask your Greenhouse admin to upgrade your access, then try again
Make sure you’re signing in to the correct Greenhouse organization
If your org restricts OAuth apps, ask your Greenhouse admin to allow Town

A write action fails

If the action is waiting on an approval card, approve it in Town first
Confirm your Greenhouse role allows that action (the assistant can’t do more than you can)

Integrations overview — How integrations give your assistant context
Routines — Automate recurring recruiting workflows