Question 1

Which Greenhouse objects can Polytomic sync?

Accepted Answer

All 68 listable objects in the Greenhouse Harvest API. That covers the ones most teams start with, candidates, applications, jobs, offers, scorecards, interviews, and job posts, and it also covers the long tail that makes real reporting possible: application stages, candidate education and employment history, notes and attachments, openings, job stage interviews and owners, interview kits and interviewers, scorecard questions and answers, departments and offices, users and permissions, approvals, custom fields, demographics and EEOC, prospects, sources and tracking links, rejection reasons, and pay inputs. You choose which of those to sync rather than taking all of them.

Question 2

Does Polytomic re-read all of Greenhouse on every sync?

Accepted Answer

No. Every object supports incremental reads, filtering on the last updated timestamp so each ETL run pulls only records that changed since the previous sync. Polytomic also subtracts a short lookback window from the cursor, because Greenhouse is eventually consistent and a record can land slightly after the timestamp it carries. That lookback trades a small amount of re-reading for not silently dropping records, which is the right trade for recruiting data feeding a data warehouse.

Question 3

Can I sync Greenhouse custom fields?

Accepted Answer

Yes, in two forms. There are dedicated collections for custom field definitions, their options, and their department and office associations, which is what you want if you are modeling the configuration itself. Separately, custom field values come through on candidates, applications, jobs, offers, openings, and users. Those values arrive as a nested object rather than being expanded into separately typed columns, so you unpack the ones you care about in your data warehouse.

Question 4

What happens when a record is deleted in Greenhouse?

Accepted Answer

Incremental syncs work from records that Greenhouse returns as updated, and the Harvest API does not provide a deletion feed, so a hard deleted record will simply stop appearing rather than being marked as removed in your destination. If deletion accuracy matters for your reporting, run a periodic full resync of the affected objects to reconcile. This is a Greenhouse API constraint rather than a Polytomic one.

Question 5

Why not just script the Greenhouse API myself?

Accepted Answer

One or two endpoints is a reasonable script. The problem is that useful recruiting analytics needs a dozen or more objects joined together, and each one brings pagination, scopes, rate limit backoff, and its own incremental cursor to maintain. Add the eventual consistency lookback and it becomes a real project to keep correct. Polytomic handles ETL from Greenhouse into your data warehouse across the whole Harvest catalog, and the same platform runs reverse ETL back out to your SaaS tools, so recruiting data can also feed the systems your team works in.

Greenhouse

Perfect pairings

Full Harvest API coverage

Incremental on every object

OAuth or your own app

Example workflows

What you can sync

From Greenhouse

To your destinations

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Greenhouse in minutes

More integrations beyond Greenhouse