Yes, 100Hires connects to Zapier. Once linked, every new candidate, stage change, or published job can fire an action in any of Zapier's 8,000+ apps. Zapier can also push data the other way to create candidates, move them through your pipeline, or assign them to a job.
This page covers what you can automate, the exact triggers and actions 100Hires exposes, the Zaps recruiters set up most, and how to connect the two in a few minutes.
The glue work between your ATS and everything else
Most recruiting teams already run a quiet pile of manual handoffs. A new applicant arrives, so someone copies them into a Google Sheet. A candidate moves to Interview, so someone updates a tracker and pings the hiring manager in Slack.
A form comes in, so someone retypes it into the ATS. Each task is small. Run them across every role, every day, and they eat hours nobody planned for.
Zapier is how teams connect tools that do not talk to each other on their own. The 100Hires Zapier integration puts your ATS on that map: pipeline events become triggers that start a Zap, and the apps you live in become the destination.
Nothing gets retyped, and the work happens whether or not anyone is watching the pipeline.
What 100Hires exposes to Zapier
The 100Hires ATS app on Zapier ships with three triggers and three actions. Triggers are events in 100Hires that start a Zap; actions are things Zapier does inside 100Hires. You combine them with any of Zapier's other apps to build a workflow.
Zaps recruiters set up most
The point of the integration is not the trigger list, it is the hours it gives back. These are the automations teams build first, each one replacing a manual handoff that used to sit on a recruiter's plate.
Zapier or native automations? You will want both
100Hires already automates a lot inside the pipeline on its own. Native workflow automations advance or reject candidates by rule, AI Score ranks applicants from 0 to 100, and nurture campaigns follow up without you.
None of that needs Zapier, and none of it counts against a Zapier task quota. It runs inside the ATS on every plan.
Use native automations for logic that lives inside the ATS, and use Zapier for the long tail of apps outside it. The Zapier app exposes candidate and job events rather than every field in 100Hires, so deep in-pipeline rules are faster to build natively.
For the full picture of what 100Hires automates on its own, see recruitment automation software. Developers who want to drive 100Hires programmatically can also use the REST API and the 100Hires MCP server, which run on the same Personal API key.
100Hires plus Zapier versus a typical ATS
Where 100Hires is not the whole answer: Zapier itself runs on its own plan, so very high task volume is billed by Zapier, not by 100Hires, and the app exposes candidate and job events rather than every object in the ATS.
For most teams the three triggers and three actions cover the handoffs that waste the most time.