HR & RECRUITING

Parse emailed resumes into structured Airtable candidate rows

Watches a hiring inbox for emails with resume attachments, extracts the candidate's name, contact, skills, and years of experience with AI.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email in hiring inbox labelGmailGmail
  • LogicConfirm message has a resume attachment
  • ActionExtract structured candidate fields via OpenAIOpenAI
  • LogicCheck Airtable for duplicate by emailAirtableAirtable
  • OutputCreate or update structured candidate row in AirtableAirtableAirtable

What it does

Converts messy inbound application emails into structured candidate records. It reads the email and its resume attachment, pulls out the fields that matter, and files a tidy row in your applicant tracker.

When to use it

Use it when candidates apply by emailing a resume to a shared hiring address and someone is manually copy-pasting details into a spreadsheet. It removes the data-entry step and standardizes every record.

How it works

  1. 1A new email in the monitored Gmail label triggers the flow.
  2. 2A logic step confirms the message has a resume attachment and is not auto-reply or spam.
  3. 3The attachment text is extracted and sent to OpenAI, which returns structured fields: name, email, phone, top skills, years of experience, and current title.
  4. 4The flow checks Airtable for an existing record with the same email to avoid duplicates.
  5. 5A new structured candidate row is created in Airtable (or the existing one is updated) with status New.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect AirtableBases, tables, views, automations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.