Applicant Tracking System Integrations to Require: Email, Calendar, E-Signature, Job Boards and HRIS

The applicant tracking system integrations to require are email, calendar, e-signature, job boards and your HRIS, plus an export route such as CSV, an API or webhooks as a safety net. Require each one to work today in the demo, not on a roadmap, and score every vendor on the same sheet.

Why integrations decide whether a tool gets used

Most hiring teams do not abandon an applicant tracking system because the pipeline view is bad. They abandon it because the work around the pipeline stays outside it. Interview invitations still go from a personal inbox, the calendar is still checked by hand, the offer still gets signed in a separate tool, and the new hire is still retyped into the HR system. Each gap is small. Together they mean the ATS becomes a place where recruiters update statuses at the end of the week, and a record that is always slightly wrong.

Integrations are the answer, but they are also where vendors are most slippery. A logo on a page does not tell you whether the connection reads data, writes data, runs in both directions, or needs a paid add-on. This guide is for small and mid-size teams choosing a system themselves. It covers the five connections worth requiring, what each should do in plain terms, how to test it, and how to score. For the wider buying picture see /applicant-tracking-system and /recruitment-software. Never take a vendor's integration list on trust, and check current features and pricing on their site and in a live demo.

The five integrations and what each should actually do

Start by being precise about what you want from each connection. "Email integration" can mean five different things, and a vendor will happily answer the easiest one.

The middle column is a floor, not a luxury. If a system cannot meet the minimum in a row, that is a gap you will fill by hand every week. The next column is where larger systems compete, and where you should decide honestly whether you will use the feature. Many small teams pay for two-way sync they never switch on.

Email: require a record, not just a send button

Hiring is mostly conversation, and most of it is email. If the conversation happens outside the system, your records are fiction. Require three things.

First, messages sent to candidates should be sent and stored from the candidate record, so a colleague opening the file sees the history. Second, replies should come back to that same record, either through a connection to your mailbox or through a reply address the system manages. Third, you should be able to send from an address your candidates will trust. A tool that sends from a generic address can land in spam, and candidates miss the one message that matters.

Also require an intake route. Many candidates apply by emailing a CV, and a recruiter who forwards those by hand is doing data entry. Look for a private address that reads attached CVs and creates candidates, and ask for the daily limits and accepted file types. Test it with a PDF, a DOCX and a CV that arrives as a link only. Finally ask what happens to emails when you leave: can you export the history, or does it stay behind? An email log you cannot take with you is a form of lock-in, which /compare explains further.

Calendar: scheduling is where recruiters lose hours

Interview scheduling is the single most repetitive task in recruiting. A good calendar integration removes the back-and-forth in one of two ways. Either the candidate picks from times you offer, or the system reads your free and busy times and proposes them.

Write down the level you need. Level one is that the candidate chooses a time and the chosen time is recorded on the candidate. Level two adds the event on your calendar with the right attendees. Level three adds a meeting link, reminders and rescheduling that updates both sides. Level three is a real build, and many vendors reach it only for one calendar provider, so ask which ones: Google, Outlook, or both.

Test the awkward cases, because the happy path always works. Ask the vendor to reschedule an interview, to book a panel of three interviewers across time zones, and to cancel after the candidate has accepted. Ask what permissions the calendar connection needs, because granting access to your whole calendar is a security decision and your IT lead may have a view. If you only run a few interviews a week, level one with a calendar entry you add yourself may be enough, and you should not pay a premium for level three.

E-signature: offers should close inside the system

The offer is the moment a hiring process is most likely to stall. A letter goes out as an attachment, the candidate prints it, signs it, scans it, and emails it back three days later. An e-signature connection shortens that, and it also gives you a dated record of who agreed to what.

Require these behaviors. The offer letter should be generated from a template with the candidate and role details filled in, so no one retypes a salary. There should be an approval step before it goes out, so a manager cannot send an unapproved figure. The candidate should be able to sign on a phone without creating an account. The signed copy should be stored on the candidate record and be downloadable. And you should be able to see status: sent, viewed, signed, declined.

Check what the vendor means by signature. Some build signing in, others connect to a separate e-signature provider that you pay for separately. Both can be fine, but the second adds a cost and a second login. Whether an electronic signature is valid for an employment contract depends on the country and sometimes the contract type, so confirm local rules with a lawyer. Our template at /offer-letter-template is a starting point for the letter itself.

Job boards: be wary of the multiposting promise

Multiposting means writing a job once and publishing it to several boards. It sounds like the most valuable integration on the list, and for high-volume hiring it can be. For most small teams it is the most overstated.

There are three separate things a vendor can mean. The first is a public apply page or link that you post wherever the board allows an outside link. The second is posting the job to boards from inside the system. The third is applicants flowing back automatically with their status. Boards control their own access, some charge for it, and some restrict direct posting to approved partners, so what a vendor offers can change. Ask for the current list of boards and whether each is free or paid.

If you do not get true multiposting, a workable fallback is common. Post the job on the boards you already pay for, point candidates to an apply link, and forward application emails that carry a CV attachment into your CV inbox. That is slower than one-click posting but it is honest, and it costs nothing extra. Decide how many boards you really use. A team that posts on two boards does not need a thirty-board network, and the time saved is a few minutes per role. Compare that against the price difference before you let a board list drive the choice.

HRIS: the handoff after the hire

The last integration matters least until the day it matters most. When a candidate accepts, someone must create an employee record, send onboarding forms and start payroll. If that means retyping name, address, start date and salary from the ATS into the HR system, you will make errors, and errors in payroll data are expensive to fix.

Require clarity on what a hire does. Does the system push a record into your HRIS directly, and in which direction does data flow? Does it support your HR system by name, or only through a generic route? Is the connection included in your plan or an add-on? For a small team without deep HR software, the most important question is different: can you take a complete record of the hire out as a single file or structured export, and can an automation tool pick up the hire event?

Be skeptical about large HRIS and payroll claims from small vendors. Deep connections to enterprise HR suites are usually built by enterprise vendors for enterprise customers. If you run one of those suites, put it first on your list and ask for a reference customer on the same one. Otherwise, a clean export plus a webhook or automation tool is a reasonable and cheaper handoff.

The safety net: API, webhooks, CSV and a scoring sheet

No vendor connects to everything you use. The question is what happens when it does not. A system with an open route out and in can bridge almost any gap. A system without one leaves you waiting for the vendor's roadmap.

Require four things as a safety net: import from CSV, export to CSV, an API with keys you can revoke, and webhooks that fire on events like a hire or an accepted offer. With those, an automation tool can connect the system to a spreadsheet, a chat tool or an HR system without custom code. Ask whether the API is read-only or can also write, whether it exposes candidate documents, and whether there is a limit on calls. Ask what the events are called and whether failed deliveries retry.

Use this scoring sheet to compare vendors. Score each row from 0 to 3, where 0 means absent, 1 means workaround only, 2 means works but with limits, and 3 means works fully today. Weight the rows by what you actually do.

Multiply score by weight, add up, and compare. Fill the sheet during the demo, not after.

One more habit helps. Ask each vendor to put its integration answers in writing after the demo, listing which connections work today, which need a third-party tool and which are planned. Keep that email with your sheet. If a connection later turns out to behave differently, you have a record, and you can raise it before the first renewal rather than after.

A worked example

Here is an example with made-up numbers, to show how weighting changes the answer. A twelve-person company hires about eight people a year and posts every role on two job boards. The hiring lead writes the weights: email 3, calendar 3, e-signature 3, apply link 3, direct posting 1, HR handoff 1, safety net 2.

Vendor A is a large suite with direct posting to many boards and a deep HR connection. Vendor B is a smaller tool with built-in email, candidate-chosen interview times, built-in signing and an API, but no multiposting. These example scores are invented to show the method.

The suite wins narrowly, but it costs more and the two features that tip it, direct posting and HR handoff, carry a weight of 1 each because this team barely uses them. Drop those two rows and Vendor B wins 36 to 34. The lesson is not that one vendor is better. It is that you should set weights before the demo, so the loudest feature does not set them for you.

Common mistakes when you assess integrations

Accepting a logo as proof. A logo on an integrations page can mean a deep connection, a one-way export, or a connector that needs a third-party tool. Ask for the real behavior.

Asking only whether it integrates. The answer is nearly always yes. Ask what data moves, in which direction, how often, and who pays.

Paying for integrations you will not turn on. Two-way sync with a system you do not use is cost with no return. List what you run today and ignore the rest.

Forgetting the exit. If email history, notes and signed offers cannot leave with you, the integration is also a lock-in. Test an export during the trial.

Skipping the security conversation. Every connection grants access. Ask what permissions a calendar or mailbox connection requests, whether keys can be revoked, and whether changes are logged. Rules on candidate data differ by country, so check local law before you connect personal inboxes or send candidate records to other tools.

Testing only the happy path. Reschedule an interview, resend a bounced email, void a signed offer. The edge cases show how the system really behaves, and they are where your team will spend its worst afternoons if the tool handles them badly.

Where Rezumz fits

Rezumz is an AI hiring workspace for small and mid-size hiring teams. It is honest to say where it meets this checklist and where it does not.

Rezumz suits small and mid-size hiring teams, and the Team plan suits four or more recruiters. It does not suit large enterprises that need deep HRIS or payroll connections, or teams that need one-click multiposting to job boards. Prices: a free plan with 2 free candidate analyses, $29 a month, $199 a year or a limited $499 lifetime plan, and Team at $79 a month or $699 a year for up to 10 teammates. See /pricing and try the live /demo.

Who this checklist is not for

If you hire fewer than five people a year, you probably do not need to score five integrations. A shared inbox, a spreadsheet and a template library can carry you, and /free-applicant-tracking-system covers the free route. If you are a large employer with a procurement team, your security and IT review will set the integration list for you, and this article is only a warm-up. If you are a high-volume recruiter who lives on job boards, put posting at the top of your sheet and weight it above everything else.

For everyone in the middle, the rule is simple. Require the connections you will use in the next six months, confirm each one in a live demo, keep a safety net of export, API and webhooks, and treat everything else as a bonus that should not move the price.