Question 1

How do incremental syncs work with Ashby?

Accepted Answer

Ashby issues a sync token with each response, and Polytomic stores it and sends it back on the next run. That makes incremental ETL reads resume exactly where the last one stopped rather than inferring a window from timestamps, which is more reliable for a recruiting system where records get edited well after they are created. Incremental is enabled for the objects most people sync heavily, including candidates, applications, feedback, interviews, jobs, offers, departments, locations, openings, projects, surveys, and users.

Question 2

Are there Ashby objects that cannot sync incrementally?

Accepted Answer

Yes, and it is worth knowing which before you schedule aggressively. Full read only objects include application hiring team roles, archive and close reasons, brands, communication templates, interview plan stages, job boards and postings, sources, source tracking links, and notetaker transcripts. These are re-read in full on every execution. Most are small configuration objects where that costs little, so a common pattern is syncing the large incremental objects frequently and the full read ones on a slower schedule.

Question 3

Can Polytomic sync Ashby interview transcripts?

Accepted Answer

Yes. Notetaker transcripts are supported even though they are not in the public connector documentation. Ashby has no endpoint that lists transcripts directly, so Polytomic discovers them through interview schedules, fetches each transcript, and emits one row per speaker turn, which is the shape you want for text analysis in a data warehouse. Transcripts are full read only, and any that have expired or been deleted in Ashby are skipped rather than failing the sync.

Question 4

How are Ashby custom fields handled?

Accepted Answer

There is a dedicated custom fields collection exposing definitions and their selectable values, and custom field values also come through on candidates, applications, jobs, and offer versions. Values arrive as an array of objects carrying the field id, title, value, label, and whether it is private. They are not flattened into individually typed columns, and the value itself is modeled as a string, so numeric or date custom fields need casting in your data warehouse.

Question 5

Why not build the Ashby integration in house?

Accepted Answer

Ashby's API is pleasant to work with, so a single endpoint is easy. The cost appears when you need twenty objects joined for real funnel reporting, each with its own sync token to persist, its own pagination, and its own decision about whether incremental is even available. Then someone has to own it when a schema shifts. Polytomic runs ETL from Ashby into your data warehouse across the full catalog, and reverse ETL from that warehouse back into your SaaS tools, so the same platform covers both directions.

Ashby

Perfect pairings

Sync token incrementals

Full recruiting catalog

Notetaker transcripts

Example workflows

What you can sync

From Ashby

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 Ashby in minutes

More integrations beyond Ashby