Send candidates to an interview slot
A completed job application returns a one-time booking link for a phone screen with the right interviewer.
New submission on your job application form
Create a single-use Calendly scheduling link for a screening interview
One-directional. A submission triggers the action — nothing is written back into your form.
Phone screens die in the scheduling. A recruiter proposes three times, the candidate is at work, two of them are gone by the time she replies, and a strong applicant cools off over four days of email. A one-time booking link removes the thread entirely.
In-house recruiters and small agencies use this on roles with steady inbound. Because the link is generated per application and tied to the interviewer for that role, nobody gets sent a shared calendar that a different team is also filling.
Setting it up
- 1
Publish the job application form in formformform and use conditional logic so Position Applied For drives the follow-up questions each role needs.
- 2
In Calendly, give each hiring manager a 20-minute screening event type and add a custom question about earliest start date, so the answer prefills rather than being asked twice.
- 3
Create the Zap with the New Submission trigger and select the application form.
- 4
Add Zapier paths on Position Applied For, one path per role, so the right interviewer's event type is used for the link.
- 5
In each path add "Create a Single-Use Scheduling Link", pick that interviewer's screening event type, and keep the maximum event count at one.
- 6
Append prefill values to the returned URL: name from Full Name, email from Email Address, and Available Start Date as the first custom question answer.
- 7
Send the link by email to Email Address with a two-line note naming the role and the interviewer, and set the Zap to skip anyone whose application is missing Relevant Skills if you screen on that first.
- 8
Run a test application through each path, confirm the correct calendar opens, then enable the Zap.
What maps where
Using the Job Application Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Calendly |
|---|---|
| Full Name | Name prefill on the single-use link, so the candidate does not retype it |
| Email Address | Email prefill, and the address the screening link is sent to |
| Position Applied For | Zapier path that selects the interviewer's screening event type |
| Available Start Date | First custom question on the screening event type, visible to the interviewer |
| City, State | Passed as a UTM value on the link so bookings can be grouped by market |
Variations worth knowing
Insert a Zapier filter on Highest Level of Education or Employment Type so only applications meeting the bar receive a link. Everyone else gets a plain acknowledgement email, and the interviewer's calendar stays clear of screens that were never going anywhere.
When a role draws hundreds of applications, swap the single-use link for "Add Invitee to a One-Off Meeting" and block out one screening session per day. Applicants are added to the next open session in order of arrival, so the recruiter works a solid morning of screens instead of a calendar cut into twenty-minute islands.
If something isn't arriving
Path conditions match on the exact answer text. If Position Applied For is a free-text field, change it to a choice list in formformform, republish, and rebuild the paths against those options so a typo cannot fall through to the first path.
Prefill only reaches custom questions that exist on that event type, in order. Add the start date question to every interviewer's screening event type and check it sits first, or the value lands on a question you were not expecting.
Frequently asked questions
Can I stop candidates booking outside the hiring window?
Set the date range on the Calendly event type rather than in the Zap. The single-use link inherits the event type's availability, so a screening window that closes on Friday closes for every link already issued that week.
How do I know which application a booking belongs to?
Prefilled name and email match the application record, and a UTM value on the link identifies the role or market. For a tighter join, write both the submission and the Calendly event to your ATS and match on email address.
What if a candidate never books their screen?
Calendly does not tell the form either way, so track it where the bookings land. Log every issued link to your ATS or a sheet in the same Zap, write the Calendly booking to the same row, and anything still open after a few days is a candidate to chase — with Work Experience and Relevant Skills already on file to judge whether it is worth it.
Related automations
- Book demos from your lead form
A prospect submits your demo request form and gets a personal booking link back, so they pick a slot themselves.
- Convert event RSVPs into 1:1 sessions
Registrants who want a follow-up consultation are placed directly on a consultant's calendar when they sign up.
- Onboard new customers automatically
A post-purchase onboarding form hands each new customer a booking link for their kickoff call.
- Put support callbacks straight on a rep's calendar
Each callback request adds the customer as an invitee on a one-off Calendly meeting with the support team.
- Route discovery calls for inbound leads
Contact form enquiries come back with a booking link for a discovery call instead of a holding reply.
- Add service appointments to the dispatch calendar
A booking arrives and lands on the dispatch calendar with the address as a map pin and the job in the title.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free