Send the offer packet the day a candidate accepts
The acceptance submission fills your DocuSign offer template and sends the letter and tax forms as one envelope.
New form submission on your offer acceptance form
Send a DocuSign envelope containing the offer letter and tax forms to the candidate
One-directional. A submission triggers the action — nothing is written back into your form.
The gap between a verbal yes and a signed offer is where candidates get re-approached. Everyone in HR knows it, and the paperwork still takes two days because someone types the role and the start date into three documents by hand.
Here the acceptance form does that typing. Position, employment type and start date land in the offer template's tabs, the candidate's personal address becomes the recipient, and DocuSign sends the letter and the tax forms as one envelope. The candidate signs on their phone the same afternoon.
Setting it up
- 1
Start from the job application template and trim it to an acceptance step: name, personal email, position, employment type and start date. Nothing else needs to be on it.
- 2
Keep the wording of the position options identical to the wording used in your DocuSign offer letter, so the two never disagree.
- 3
In DocuSign, build one template holding the offer letter and your tax forms as separate documents, so the candidate signs a single envelope instead of three.
- 4
Add text tabs on the offer letter for job title, employment basis and start date, and mark every signature tab on the tax forms as required.
- 5
In Zapier, set formformform's New Submission event as the trigger and choose the acceptance form.
- 6
Add the DocuSign action that creates and sends an envelope from a template, then select the offer packet template.
- 7
Map Email Address to the recipient email — use the candidate's personal address, since the work account does not exist yet.
- 8
Run a dummy candidate through, check the start date renders in the format the template expects, then 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 | DocuSign |
|---|---|
| Full Name | Recipient name and the offer letter signature block |
| Email Address | Recipient email the signing packet is sent to |
| Position Applied For | Job title text tab in the offer letter |
| Employment Type | Employment basis tab (full-time, part-time, contract) |
| Available Start Date | Start date tab on the letter and the tax forms |
Variations worth knowing
Add the hiring manager as a carbon-copy recipient on the same envelope. They receive the executed packet without having to sign anything, which saves the usual round of "has she signed yet" messages to HR.
Filter on Employment Type and send contractors your contractor agreement template instead of the employee packet. One acceptance form, two DocuSign actions, and nobody signs the wrong set of tax forms.
If something isn't arriving
Insert a Zapier Formatter step between the trigger and the DocuSign action that converts Available Start Date into the written format your template expects, then map the formatted output rather than the raw value.
Check the envelope status in DocuSign first, since bounced addresses show up there. A typo in Email Address cannot be corrected from the form, so void the envelope, fix the address and resend from DocuSign.
Frequently asked questions
Can HR countersign the offer letter?
Yes. Add your HR signatory as a second recipient with routing order two. The candidate signs first, HR countersigns, and DocuSign only marks the envelope complete once both signatures are in place.
Are the tax forms attached by the form?
No, and they should not be. The packet is what you send the candidate, so every document in it lives inside the DocuSign template. Upload fields do exist in formformform — add one when you want something back from the candidate, such as ID or proof of right to work, up to 2 MB per file — but those files land on the response for you to download rather than inside the envelope, because an envelope created from a template always carries the template's own documents.
Where do the completed documents end up?
In DocuSign, not in the form. Nothing is written back into formformform, since the connection runs one way. Most HR teams point DocuSign at their existing document storage so the executed packet files itself.
Related automations
- Get the order spec signed before production starts
Every order builds a DocuSign purchase agreement with the exact spec, so the customer authorises it before anything is cut.
- Send a liability waiver to every workshop registrant
Each workshop registration sends a DocuSign waiver to the attendee, signed and filed well before the event date.
- Send an NDA before every demo call
Every demo request generates a DocuSign envelope carrying your mutual NDA, addressed to the person who asked for the call.
- Send lease disclosures to every rental applicant
Each rental application sends the required disclosures and lease document to the applicant for signature.
- Turn a project scope request into a signed contract
A scope request populates your services agreement template and goes out for signature without an account manager touching it.
- Append every support request to a running log
Every help desk submission appends a line to one shared Dropbox text file, so the team reads the day's requests in order.
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