Use cases → Documents and Drive
Route inbound CVs into a hiring pipeline folder
Automatically collect candidate CVs from email and place them in a shared Drive folder for the hiring team.
| Who it is for | Recruiters and HR teams automating candidate intake. |
|---|---|
| APIs | Gmail API, Drive API |
| Typical scopes | gmail.readonly, drive |
The problem
CVs arrive scattered across inboxes and aliases, easily missed or misfiled. Manual download and upload is slow, error-prone, and risks leaking private data in the wrong folder.
How it works
- Monitor the recruitment mailbox using a service account via domain-wide delegation.
- Filter for new candidate emails using subject, sender, or attachment type.
- Extract CV attachments and upload each to the correct Drive folder.
- Set Drive permissions so the hiring panel can access but not edit originals.
What changes
Every candidate CV lands in the right pipeline folder, ready for review, without manual handling or mailbox sifting.
Questions people ask
Can I process multiple attachments in a single message?
Yes, but filenames can clash. Always rename or namespace attachments before Drive upload to avoid overwrites.
How do I avoid duplicates?
Track the Gmail message ID and Drive file ID together. Reprocessing can otherwise create silent duplicates if the workflow restarts.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Create a client folder structure the moment a deal closes
Provision a consistent Drive folder tree, seeded with templates and shared with the right people, automatically.
Generate documents from a template and real data
Produce agreements, letters and reports from a Docs template with fields filled from your systems.
Sort incoming files into the right place automatically
Watch a drop folder, work out what each file is, and file it where it belongs with a consistent name.