Skip to content

Make integration · HTTP module

Parse resumes in Make scenarios

Make’s HTTP module can send a CV to HireLayer and map the JSON it gets back, with no custom app to install. Combine it with Gmail, Google Drive, Google Sheets, Slack or your ATS to screen candidates automatically.

Module
HTTP › Make a request
Authentication
API key in the X-API-Key header
Timeout to set
300 seconds (parsing takes about 35)
Cost
1 credit per parse or score; criteria are free
Make + HireLayer
  1. 1Watch emails or filesMakeGmail Watch emails with attachments, Google Drive Watch files, or a webhook from a form.
  2. 2HTTP › Make a requestHireLayerPOST the file to /api/v4/resumes/parse as multipart/form-data. HireLayer answers with the candidate JSON.
  3. 3Score against the jobHireLayerA second HTTP module sends the resume’s application_id and your job to HireLayer Resume Scorer.
  4. 4Write the resultsMakeGoogle Sheets Add a row, Slack Create a message, or the update module of your ATS.

Scenarios teams run with HireLayer and Make

  • Shared CV inbox to a spreadsheet

    Gmail Watch emails → Iterator on attachments → HTTP Make a request to HireLayer → Google Sheets Add a row with name, email, phone, job title and skills.

  • Score every application

    Parse the CV, then send its application_id and the job to Resume Scorer. A router sends scores above 0.7 to the hiring manger and files the rest.

  • Folder of CVs to a ranked shortlist

    Google Drive Search files → Download a file → parse each CV → Array aggregator → one Resume Scorer call with precise_ranking on, each candidate with a ranking reason.

  • Clean skills for reporting

    Send free-text skills to the skills API and store standard names, so “React.js” and “ReactJS” count as the same skil in your dashboards.

Configure the HTTP module

You need a Make account and a HireLayer API key (free plan: 50 credits a month, no card).

  1. 1

    Add a keychain for your API key

    Add an HTTP › Make a request module. In Authentication type choose API key, create a keychain, set the key placement to the header, the header name to X-API-Key, and paste your HireLayer key.

  2. 2

    Set the request

    URL https://hirelayer.co/api/v4/resumes/parse, method POST, body content type multipart/form-data. Add a File field named file and map the file name and data from the previous module, for example a Gmail attachment. If you recruit for several client companies, add a HireLayer-Workspace header with the client’s id, so each client’s candidates are stored apart; without it they go to your default workspace.

    HTTP › Make a requesttext
    URL                https://hirelayer.co/api/v4/resumes/parse
    Method             POST
    Authentication     API key (header X-API-Key)
    Headers            HireLayer-Workspace ← optional, your client’s id
    Body content type  multipart/form-data
    Fields             file            ← File: name + data from the trigger
                       application_id  ← optional, your reference
    Parse response     Yes
    Timeout            300
  3. 3

    Raise the timeout

    Set Timeout to 300 seconds, the maximum Make allows. Parsing usually takes about 35 seconds and can take more than a minute on long scanned files.

  4. 4

    Map the response

    Turn on Parse response and run the module once: the data structure appears, and fields like resume.info_candidate.full_name or application_id become available to the next modules.

Response fields to map

HireLayer fieldMake mapping (module 2 = HTTP)Note
resume.info_candidate.full_name{{2.data.resume.info_candidate.full_name}}
resume.info_candidate.email{{2.data.resume.info_candidate.email}}
resume.info_candidate.phone_number{{2.data.resume.info_candidate.phone_number}}
resume.info_candidate.job_title{{2.data.resume.info_candidate.job_title}}
resume.skills[].skill_title{{join(map(2.data.resume.skills; "skill_title"); ", ")}}
application_id{{2.data.application_id}}Input of the scoring call

Score the parsed candidate

Add a second HTTP › Make a request module with the same keychain and HireLayer-Workspace header, body type Raw, content type JSON and the request content below. The parse already stored the resume, so its application_id stands for it. Extract the criteria once per job with HireLayer Job Criteria Extractor (POST /api/v4/jobs/extract-criteria, free) under your own job_id, so every applicant is scored on the same list. The answer’s scores[] holds the score, verdict and summary.

Request content, sent to POST https://hirelayer.co/api/v4/resumes/scorejson
{
  "job": { "job_id": "senior-react-paris" },
  "resumes": [
    { "application_id": "{{2.data.application_id}}" }
  ]
}

Good to know

  • Default timeouts are too short

    A request left at a short timeout fails on most CVs. Allways set 300 seconds on the parsing and scoring modules.

  • Score by application_id

    The parse stores the resume, so the scoring call sends its application_id rather than the resume text: there is nothing to escape in the JSON body, and scoring the same resume against the same job again costs nothing.

  • File size

    HireLayer accepts files up to about 4.5 MB, below the 5 MB file limit of Make’s free plan, so any plan works.

  • Results in the job’s language

    Criteria, summaries and ranking reasons follow the job’s language when it is English, French, German, Spanish or Portuguese, and are in English otherwise; scores and field names are language-neutral.

HireLayer and Make: questions

Is there a HireLayer app in Make?

Not in Make’s public app list yet. The HTTP › Make a request module covers every HireLayer product today: parsing, criteria extraction, scoring and ranking, the two searches and skills.

How do I send a file to an API from Make?

In HTTP › Make a request, choose multipart/form-data as the body content type, add a field of type File named file, and map the file name and data from the module that produced the file.

Why does the HTTP module time out?

Resume parsing takes about 35 seconds, sometimes more than a minute for long scans. Set the module timeout to 300 seconds.

Can I parse attachments from Gmail or Outlook?

Yes. Watch emails, iterate over the attachments, and send each one to HireLayer. Filter on the file extension to skip images in signatures.

Is candidate data stored by HireLayer?

Add a do_not_store_data field set to true and HireLayer keeps no copy of the file; the parsed data is still returned. Processing runs in the EU.

Connect Make to HireLayer today

The Free plan includes 50 credits a month, no card required. Parsing a resume costs one credit, scoring one per resume evaluated, and extracting job criteria is free.