Power Automate integration · Custom connector
Parse resumes in Power Automate
Import the HireLayer connector once, then parse CVs from Outlook attachments, SharePoint libraries or OneDrive folders, score candidates against a job, and write the results to Excel, Dataverse, Teams or your ATS.
- Connector file
- OpenAPI 2.0 (Swagger), 7 actions
- Authentication
- API key, asked when you create the connection
- Works in
- Power Automate, Power Apps, Copilot Studio
- License
- Custom connectors need a Premium plan
- 1When a new email arrivesPower AutomateOutlook trigger with attachments, or When a file is created in a SharePoint library or a OneDrive folder.
- 2HireLayer · Parse a resumeHireLayerMap the attachment content into Resume file. The action returns the candidate as dynamic content.
- 3HireLayer · Score resumes against a jobHireLayerScores the parsed resume, by its Application ID, against the job and returns a score from 0 to 1.
- 4Store and notifyPower AutomateAdd a row to an Excel table or a Dataverse table, then post an adaptive card in Teams.
Flows you can build
Recruiting mailbox to Excel
Each CV sent to the shared recruiting mailbox becomes a row in an Excel table on SharePoint, with contact details, current title, languages and skills.
SharePoint CV library
When a recruiter drops a CV into a document library, the flow parses it and fills the library columns, so the list view becomes searchble.
Shortlists in Teams
Score each applicant against the job and post the strong matches to the hirring channel with the summary and the main criteria met.
Recruiting copilot
The same connector is available in Copilot Studio, so an agent can parse a CV, rank candidates or search the talent pool when a recruiter asks.
Import the connector
Creating a custom connector needs a Power Automate plan with Premium connectors. Each user who runs the flow creates a connection with their own HireLayer key.
- 1
Download the definition
Download the HireLayer connector file (OpenAPI 2.0). It describes seven actions: Parse a resume, Extract job criteria, Score resumes against a job, Search the talent pool, Find jobs for a resume, Normalize skills and Get account.
- 2
Create the custom connector
In Power Automate, open Custom connectors → New custom connector → Import an OpenAPI file, name it HireLayer and select the file. Security is already set to API key in the X-API-Key header. Select Create connector.
- 3
Create a connection
Add a HireLayer action to a flow and paste your API key when asked. Get account is free, so it is a safe first test.
- 4
Map a file
In Parse a resume, map Attachments Content from Outlook or File Content from SharePoint or OneDrive into Resume file. The response appears as dynamic content: Full name, Email, Phone number, Application ID and more. To score the candidate, map Application ID into Score resumes against a job, with the Job ID that Extract job criteria returned. If you recruit for several client companies, set Workspace to the client’s id in every action, so each client’s candidates are stored apart.
Dynamic content after Parse a resume
| HireLayer field | Dynamic content label | Note |
|---|---|---|
| resume.info_candidate.full_name | Full name | |
| resume.info_candidate.email | ||
| resume.info_candidate.phone_number | Phone number | |
| resume.info_candidate.job_title | Job title | |
| resume.work_experiences[] | Work experiences | Use Apply to each |
| application_id | Application ID | Input of Score resumes against a job |
What the connector declares
The file is a standard OpenAPI 2.0 definition. You can read it before importing it, and edit the action names if your team prefers other labels.
"basePath": "/api/v4",
…
"/resumes/parse": {
"post": {
"operationId": "ParseResume",
"summary": "Parse a resume",
"consumes": ["multipart/form-data"],
"parameters": [
{ "name": "file", "in": "formData", "type": "file", "required": true,
"x-ms-summary": "Resume file" },
{ "name": "application_id", "in": "formData", "type": "string",
"x-ms-summary": "Application ID" },
{ "name": "HireLayer-Workspace", "in": "header", "type": "string",
"x-ms-summary": "Workspace" }
]
}
}Good to know
Within the 2-minute limit
Power Automate waits up to 120 seconds for an action. Parsing usually takes about 35 seconds and scoring a batch of resumes about a minute, so each action returns its result directly.
Test inside a flow
The Test tab of the connector editor does not always send files correctly. Test Parse a resume from a flow with a real attachment instead.
Retries
Power Automate retries actions that fail with a 5xx or 429 status. Failed calls are not charged. A parse that outlasts the 120-second wait can still finish and be charged; sent again once that parse is stored, the same file costs nothing.
Not a certified connector
This is a custom connector you import into your environment. It is not listed in the Microsoft conector gallery.
HireLayer APIs used on this page
HireLayer and Power Automate: questions
Is there a HireLayer connector for Power Automate?
Can Power Automate parse resumes from Outlook attachments?
Do I need a Premium license?
Can I use it in Copilot Studio?
Can I use it in Azure Logic Apps?
Connect Power Automate 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.
Other integrations
- MakeParse CVs and score candidates in Make scenarios with the built-in HTTP module and a HireLayer API key.
- Google SheetsTurn a Google Drive folder of CVs into one row per candidate, and score or normalize skills with sheet formulas.
- SalesforceTurn CVs uploaded to Salesforce into Contact fields and scores, with an Apex Queueable job and a Named Credential that holds your API key.