Stage each application as a draft for the hiring manager
Each new application lands as a Gmail draft addressed to the hiring manager, filled in and waiting for a human to press send.
New job application submission
Gmail creates a draft addressed to the hiring manager
One-directional. A submission triggers the action — nothing is written back into your form.
Recruiting teams rarely want mail going to a hiring manager untouched. The wording shifts with the role, and half the applications need a line of context added — third one this week from the same agency, or worth a look despite the gap in dates.
A draft is the compromise. Gmail's Create Draft action writes the message into the recruiter's own drafts folder, so it can be edited, forwarded or deleted with nobody outside seeing it. Small in-house teams hiring for two or three open roles get the most out of it.
Setting it up
- 1
Publish the application form with a File Upload field so candidates attach the CV itself, and add a URL field beside it for a portfolio — uploads are capped at 2 MB per file, which a CV clears easily and a case-study deck usually does not.
- 2
In Zapier, start with the formformform New Submission trigger and select the application form.
- 3
Add Gmail's Create Draft action rather than Send Email, and connect the recruiter's own account — the draft appears in that mailbox, nowhere else.
- 4
Put the hiring manager's address in To. Nothing leaves until a person opens the draft, so it is safe to set this before the wording is final.
- 5
Build the subject from Position Applied For and Full Name, so the drafts folder sorts by role at a glance.
- 6
Lead the body with Relevant Skills and Available Start Date, then Work Experience, then Cover Letter quoted underneath, and the portfolio URL on its own line. The uploaded CV stays on the response in formformform, where only your own account can open it, so download it there and attach it to the draft — a draft exists precisely so a person can add something before it goes out.
- 7
Leave Reply-To empty and put Email Address in the body instead — the manager's reply should reach the recruiter, not go straight to the candidate.
- 8
Add a Zapier path on Position Applied For so engineering applications address one manager and sales another, then test each branch and turn the Zap on.
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 | Gmail |
|---|---|
| Position Applied For | Subject line, so drafts group by role |
| Full Name | Subject line and the opening line of the draft |
| Relevant Skills | Body — the summary line the manager reads first |
| Work Experience | Body, under a background heading |
| Cover Letter | Body, quoted below the summary |
| Available Start Date | Body, beside the candidate's name |
Variations worth knowing
Add a Gmail Send Email action alongside the draft, addressed to Email Address, confirming the application arrived and naming the role. The candidate hears back immediately; the hiring manager's message still waits for a person to review it.
Put a Digest by Zapier step between the trigger and Gmail, releasing on a Friday. The draft then lists the week's candidates in one message, which suits a manager who reviews in a single sitting rather than as applications land.
If something isn't arriving
Gmail creates the draft in whichever account Zapier is connected to, not the address in the To field. Reconnect the action using the recruiter's account, or a delegated account they have access to, and test again.
Line breaks collapse when the body is treated as HTML. Switch the Gmail action's body type to plain, or keep HTML and let the field carry its own paragraph markup — then re-run the test to check the spacing.
Frequently asked questions
Does the candidate know a draft was created?
No. Creating a draft sends nothing. The message sits in the recruiter's drafts folder until someone opens it and presses send, and the candidate sees only whatever a person chooses to send them.
Can candidates upload a CV to the form?
Yes. Add a File Upload field and the CV arrives attached to the application, stored on the response for you to preview or download, and encrypted along with every other answer if the form is encrypted. Two things shape how you build the Zap: the ceiling is 2 MB per file, so keep a URL field alongside for a portfolio or a full-resolution piece of work; and what travels to Gmail is the answer set rather than the document, so the draft carries the links and you attach the CV from the response before sending.
Do the hiring manager's edits go back into the application?
No. The flow runs one way, from submission into Gmail. Edits, notes and forwarded threads stay in the mailbox, and the response stored in formformform is unchanged from what the candidate submitted.
Related automations
- Confirm every RSVP with the joining details
Registrants get a confirmation carrying the joining details, and the organiser mailbox is BCC'd on every one.
- Email an order confirmation to every buyer
Every order form submission sends the buyer a confirmation listing what they ordered and how it will reach them.
- Email every support request to your shared inbox
Each support request arrives as an internal email, CC'd to the on-call rep, with the customer set as Reply-To.
- Route feedback to the right team and label it
Feedback reaches the alias that owns it, labelled and laid out so a triage pass takes seconds.
- Send an instant reply to every new lead
Every quote request gets a personalised reply from your Gmail account within seconds of the form being submitted.
- Add every event signup to your Outlook contacts
Everyone who registers is written into your Outlook address book with their phone, employer and job title already filled in.
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