HR & RECRUITING

Screen inbound job applications from Gmail into a Notion pipeline

Watches a Gmail hiring inbox for new applications, uses AI to parse the resume and rank fit against the role.

CategoryHR & Recruiting
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew application email in Gmail hiring labelGmailGmail
  • ActionExtract resume attachment and email bodyGmailGmail
  • ActionParse resume and score role fit with AIOpenAI
  • LogicKeep only candidates above score threshold
  • OutputCreate candidate row in Notion pipelineNotionNotion

What it does

Turns a messy hiring inbox into a structured candidate pipeline. Every new application email is parsed, scored for role fit, and written to Notion as a ready-to-review record — no manual copy-pasting from PDFs.

When to use it

Use it when applicants email resumes directly (careers@ or a forwarded job board alias) and your recruiter is drowning in attachments. Best for small teams hiring against one or two open roles who manage candidates in Notion rather than a full ATS.

How it works

  1. 1A new email arriving in the watched Gmail label triggers the run.
  2. 2The flow extracts the resume attachment and email body text.
  3. 3OpenAI parses contact details, work history, and skills, then scores fit against the role's must-have criteria, returning a 1-100 score and a two-line summary.
  4. 4A filter checks the score is above the minimum threshold and that a resume was actually attached.
  5. 5Qualifying candidates are created as a new row in the Notion candidates database with score, summary, and stage set to "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 NotionPages, databases, comments.
  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.