Add Google Sheets rows for new CandidateZip-parsed resume attachments in Gmail.
When a new resume attachment is received in Gmail, parse it with CandidateZip and add the structured data as a row in Google Sheets.
See all CandidateZip Resume/Job Parser + Gmail integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
CandidateZip Resume/Job Parser Explore CandidateZip Resume/Job Parser →
TriggersFires when CandidateZip Resume/Job Parser finishes extracting data from a document such as an invoice, receipt, form or resume.
Posts a file to CandidateZip Resume/Job Parser to be parsed.
Runs an extraction template in CandidateZip Resume/Job Parser against a document.
Gmail Explore Gmail →
TriggersFires when a new email arrives in Gmail.
Fires when an email is sent from Gmail.
Fires when a tracked email sent via Gmail is opened.
Fires when an email sent via Gmail bounces.
Sends an email via Gmail.
Creates a draft email in Gmail.
Applies a label or folder to an email in Gmail.
Moves an email into a different folder in Gmail.
Common questions
Can Knit build “Add Google Sheets rows for new CandidateZip-parsed resume attachments in Gmail.” between CandidateZip Resume/Job Parser and Gmail?
Yes — describe it in the box above and Knit's Integrations Agent researches CandidateZip Resume/Job Parser and Gmail's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.