Put candidate interviews on the hiring team's calendar
A shortlisted candidate chooses an interview window and the event appears on the hiring calendar, Meet link included.
New submission on your interview scheduling form
Create a detailed event with the candidate as a guest and a Google Meet link attached
One-directional. A submission triggers the action — nothing is written back into your form.
Shortlisting is quick. The scheduling afterwards is what drags — six emails to agree on Tuesday at two. Send the chosen candidates a short form instead, let each one pick the window that suits them, and the interview is on the hiring team's calendar seconds later with a Meet link already in the invitation.
Recruiters running several roles at once feel the difference first. The panel stops forwarding availability threads, and the candidate receives a proper invitation rather than a note saying someone will be in touch.
Setting it up
- 1
Start from the job application template, then add an interview date question and an interview window question to the copy you send shortlisted candidates. Those two answers drive the event start.
- 2
Publish it as its own interview scheduling form, separate from the open application, so the two response lists do not mix.
- 3
Create a Zap with formformform as the trigger app, New Submission as the event, and that interview form as the source.
- 4
Add Google Calendar's Create Detailed Event action and choose the shared hiring calendar rather than the recruiter's personal one.
- 5
Set the start from the interview date and window, set the end by adding your standard first-round length, and confirm the Zap's timezone matches the panel's.
- 6
Write the summary as Position Applied For plus Full Name, so the week reads as a list of roles rather than a list of strangers.
- 7
Switch on the conference option so Google Calendar attaches a Meet link, then map Email Address to attendees so the candidate receives it.
- 8
Keep the description factual — Phone Number and Available Start Date only — because every guest on the invitation can read it.
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 | Google Calendar |
|---|---|
| Full Name | Second half of the event summary on the hiring calendar |
| Position Applied For | First half of the summary, so the panel sees which role each block belongs to |
| Email Address | Guest on the event, which sends the invitation and the Meet link |
| Phone Number | Event description, as the fallback if the candidate does not join the call |
| Available Start Date | Event description, so the panel knows the notice period before they ask |
Variations worth knowing
Put Position Applied For into a Zapier paths step and send each role's interviews to its own Google Calendar. Hiring managers subscribe only to the roles they own, and a busy engineering pipeline does not bury three marketing interviews.
Add the interviewers' addresses as fixed guests alongside Email Address. Everyone who needs to be in the room is invited by the same action, and Google Calendar shows the panel's own conflicts before anyone accepts.
If something isn't arriving
Create Detailed Event only adds a conference when the option is set in the action, and the Google account connected to Zapier must be allowed to create Meet links on that calendar. Reconnect with an account that owns the hiring calendar and re-run the test.
The form does not know what is already booked. Offer fewer windows per round, and add a Find Event step before the create action so a clash routes to an email asking the second candidate to choose again.
Frequently asked questions
Can the candidate see the internal notes on the interview?
Guests can read the event description, so keep scoring, salary bands and panel commentary out of it. Map only what the candidate would expect to see, and leave the rest in formformform responses where the hiring team reads it.
Does the candidate's answer update if we reschedule?
No. Moving the event in Google Calendar notifies the guest but changes nothing in the form — the connection only runs from a submission outwards. The response stays as the record of the window they originally chose.
Can we schedule interviews for candidates who applied months ago?
Send them the interview form as a fresh link. The Zap fires on new submissions, so an old application will not trigger anything; the candidate picking a window now is what creates the event.
Related automations
- 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.
- Block time for the calls customers ask for
Someone asks for a call, and a block appears on the rep's calendar with the customer invited and their question attached.
- Book consultations at the slot the client picked
A prospect picks a date and a time on your request form, and the consultation lands on your calendar with them invited.
- Log project deadlines as all-day events
A new project brief writes its deadline onto the production calendar as an all-day event the whole team can see.
- Turn event registrations into calendar invitations
Someone registers for your workshop and Google Calendar sends them the invitation, with their details in the event.
- Book a new patient's first visit from their intake form
A finished intake form books the patient's first visit in Acuity Scheduling and carries their contact details into the appointment.
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