Town is an AI assistant for work that connects to the tools your team already uses — email, calendar, CRM, and now Greenhouse Recruiting. Town's agents can answer questions, prepare summaries, and take actions across those tools on your behalf. The Greenhouse integration gives Town secure, permission-aware access to your hiring data so your team can work their pipeline conversationally.
Town's integration with Greenhouse Recruiting allows users to view jobs, candidates, applications, scorecards, offers, and scheduled interviews, and — with explicit per-action approval — move candidates between stages, reject or unreject applications, add internal notes, schedule or update interviews, and update candidate or job details.
Configure the Town integration
Before you begin: the person connecting Town to Greenhouse must be a Site Admin in Greenhouse Recruiting. Greenhouse list endpoints only return data for Site Admin users, so a connection made by any other user type will appear connected but return no results.
In Town, open Powers > Integrations and find Greenhouse.
Open the Greenhouse page and click Add account.
Give the connection a label (for example "Greenhouse") and click Continue. Town's assistant uses this label to pick the right account.
You'll be redirected to Greenhouse. Review the requested permissions and sign in as a Site Admin.
Click Authorize.
You'll be returned to Town, and the page will confirm Greenhouse is connected.
That's the entire setup. A few things worth knowing:
- Town is not a sync integration — it does not copy or mirror your Greenhouse data into another system. It reads data on demand when a user asks a question.
- Town writes only when a user approves a specific action (details below).
Data Town can read
Always capped by the connected user's own Greenhouse permissions:
- Jobs and their interview stages
- Candidates
- Applications
- Scorecards
- Offers
- Scheduled interviews
- Users (for interviewer lookup)
- Your organization's rejection reasons
Data Town can modify
Each action requires explicit user approval inside Town before it executes:
| Action | Greenhouse data affected |
| Move application | Application stage (or job, when transferring) |
| Reject / unreject application | Application status and rejection reason |
| Add note | A new internal note on a candidate |
| Create / update / delete interview | Scheduled interviews (time, interviewers, location) |
| Update candidate | Basic profile fields (name, company, title) |
| Update job | Job details |
- Town never sends rejection emails and never creates jobs.
- Stage moves and interview changes may still trigger notifications your organization has configured in Greenhouse — exactly as if the change were made in the Greenhouse UI.
Use the Town integration
Once connected, you work with Greenhouse by asking Town in plain language — in chat or inside automated routines.
Ask about your pipeline
For example: "How many candidates are in the onsite stage for the Account Executive role?" or "Summarize the scorecards for Jane Doe's application."
Town looks up the live data in Greenhouse and answers with specifics.
Take a hiring action — with approval
For example: "Reject Sam's application with our Unresponsive reason."
Town prepares the action and shows an approval card describing exactly what will change in Greenhouse. Nothing happens until the user clicks Allow; rejecting the card cancels the action with no change in Greenhouse.
The approved change lands in Greenhouse immediately. Here, the candidate has advanced to the Phone Interview stage:
Every action that modifies Greenhouse gets its own approval card — including each step of a multi-step request:
Schedule interviews
For example: "Schedule the phone screen for Jane Doe tomorrow at 2pm with Alex."
Town finds the interviewer in Greenhouse, drafts the interview, and asks for approval before creating it.
Add context for your team
For example: "Add a note to Jane Doe's profile: strong portfolio, prioritize for onsite."
Notes are internal to Greenhouse and visible per your organization's note-visibility settings.
Additional resources
For additional information not covered here, reach out to support@corp.town.com or visit https://www.town.com/docs.
FAQ
- Who can connect? A Greenhouse Site Admin. All of Town's access runs on that user's permissions — Town can never see or do more than the connected user can in Greenhouse.
- How do I disconnect? In Town, open Powers > Integrations > Greenhouse and remove the account. Town's Greenhouse access ends immediately and its Greenhouse tools are removed.
- Does Town act without asking? No. Every action that changes Greenhouse data requires explicit approval in Town each time, including inside automated routines.
- My connection stopped working. Town automatically keeps the connection's credentials fresh, so this should be rare — if it does happen (for example, access was revoked in Greenhouse), just reconnect from Powers > Integrations.