Agents In Use
What’s new todayLast update
108 use cases added today

Use n8n to match jobs against a resume

The builder vika2210 created a job-matching agent that uses a resume as context instead of relying only on a requested job title.

Source published dev.toAgent: n8n
FROM THE SOURCE

Original prompt

Shared by the source author. See source notes for context.

You always return a clean JSON object for use in filters.

Evidence at a glance

Sourced account
Source author
vika2210
Original account
Read the source ↗
Published
Source link checked
Reported result
The builder reports resume-aware Indeed results saved to Google Sheets and emailed to the candidate; the account does not report submitted applications.
Human involvement
No application submission or approval step is described.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. Ingest the CV from Google Drive.
  2. Extract role and location with profile context.
  3. Fetch listings and deliver matching jobs.

The builder vika2210 created a job-matching agent that uses a resume as context instead of relying only on a requested job title. A Google Drive folder receives the CV. The workflow downloads the PDF, extracts and splits its text, creates embeddings and stores the profile in Pinecone.

A message to the agent supplies the requested role and location. The AI Agent combines that request with the candidate profile and outputs structured search intent. Bright Data retrieves Indeed listings, while the workflow saves results in Google Sheets and emails the candidate. The post includes workflow screenshots, a demonstration link and a GitHub JSON artifact.

The implementation required resolving specific integration problems: keeping resume context consistent, making the agent return JSON instead of free text and mapping snapshot results into clean spreadsheet rows. The model roles were divided between embeddings, agent reasoning and job-description summaries. The demonstrated result is a personalized list, not submitted applications or an employment outcome. No candidate approval checkpoint before the email delivery is described.

Prompt
Original prompt

Source: dev.to · vika2210

Frequently asked questions

What supplied candidate context?

Resume text stored as Pinecone embeddings.

Which job source was queried?

Bright Data retrieved Indeed listings.

What integration problems needed fixing?

The builder worked on JSON-only agent output, consistent resume context and clean mapping of Bright Data results into Sheets.

More details

About this account

The AI Agent interprets the request against resume context.

Firsthand account opened and read; outcomes attributed to the author. Prompt is a verbatim excerpt of the shared original, not the complete instruction. Original workflow: https://github.com/victorias22/job-matching-agent/blob/main/My%20workflow%202.json

Credit: vika2210

Source published

Added to Agents In Use

Source checked

Tools and topics

n8n AI Agent · Google Drive · Pinecone · OpenRouter · Bright Data · Google Sheets · Gmail

Job matching · Resume profiles · Pinecone

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.