Integration
Connect Hero Parser to Emailr
When something happens in Hero Parser, your agent does the next thing in Emailr. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Hero Parser and Emailr to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Hero Parser and Emailr
Triggers and actions 2 triggers ยท 24 actions
Trigger
New CandidateTriggers when a new candidate is created (CV parsed).
- New Recruitment
Triggers when a new recruitment is created.
- Create Recruitment
Create a Recruitment in the system.
- Delete resumes
Delete resumes for a recruitment. DELETE /cv/{recruitmentId}
- Get candidate
Get candidate details by id. GET /candidate/{candidateId}
- Get recruitment
Get recruitment details by id. GET /recruitment/{recruitmentId}
- List candidates
Get list of candidates by recruitment. GET /candidate/recruitment/{recruitmentId}/list
- List recruitments
Get the recruitments list. GET /recruitment
- List resumes
Get list of resumes by recruitment. GET /cv/{recruitmentId}
- Process resumes
Process selected resumes for a recruitment (AI parsing). POST /cv/process/{recruitmentId}
- Send candidate feedback
Send feedback to selected candidates. POST /candidate/{recruitmentId}/send-feedback
- Update candidate status
Change status for selected candidates. POST /candidate/{recruitmentId}/change-status
- Update recruitment
Edit an existing recruitment. POST /recruitment/{id}
- Upload CV
Upload a CV to existing recruitment.
Action
Add contactCreate a contact. POST /v1/contacts
- Add segment
Create a contact segment. POST /v1/segments
- Add template
Create an email template. POST /v1/templates
- Delete contact
Delete a contact by ID. DELETE /v1/contacts/{id}
- Delete segment
Delete a segment by ID. DELETE /v1/segments/{id}
- Delete template
Delete a template by ID. DELETE /v1/templates/{id}
- Get contact
Fetch a contact by ID. GET /v1/contacts/{id}
- Get template
Fetch a template by ID. GET /v1/templates/{id}
- List segments
List contact segments. GET /v1/segments
- Update contact
Update a contact by ID. PUT /v1/contacts/{id}
- Update segment
Update a segment by ID. PUT /v1/segments/{id}
- Update template
Update a template by ID. PUT /v1/templates/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews