Integration
Connect Hero Parser to DNSFilter
When something happens in Hero Parser, your agent does the next thing in DNSFilter. 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 DNSFilter 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 DNSFilter
Triggers and actions 6 triggers ยท 19 actions
Trigger
New CandidateTriggers when a new candidate is created (CV parsed).
Trigger
New RecruitmentTriggers when a new recruitment is created.
Action
Create RecruitmentCreate a Recruitment in the system.
Action
Delete resumesDelete resumes for a recruitment. DELETE /cv/{recruitmentId}
Action
Get candidateGet candidate details by id. GET /candidate/{candidateId}
Action
Get recruitmentGet recruitment details by id. GET /recruitment/{recruitmentId}
Action
List candidatesGet list of candidates by recruitment. GET /candidate/recruitment/{recruitmentId}/list
Action
List recruitmentsGet the recruitments list. GET /recruitment
Action
List resumesGet list of resumes by recruitment. GET /cv/{recruitmentId}
Action
Process resumesProcess selected resumes for a recruitment (AI parsing). POST /cv/process/{recruitmentId}
Action
Send candidate feedbackSend feedback to selected candidates. POST /candidate/{recruitmentId}/send-feedback
Action
Update candidate statusChange status for selected candidates. POST /candidate/{recruitmentId}/change-status
Action
Update recruitmentEdit an existing recruitment. POST /recruitment/{id}
Action
Upload CVUpload a CV to existing recruitment.
Trigger
Blocked Page Form SubmittedTriggers when a user submits the form on the blocked page.
Trigger
Blocked Page VisitedTriggered when someone in your DNSFilter account hits a blocked page.
Trigger
Invoice AvailableTriggered when a new DNSFilter invoice becomes available.
Trigger
Policy ChangedTriggered when a DNSFilter policy is created or changed.
Action
Add to Allow ListAdds a single domain to a DNSFilter policy's allow list, with a note explaining why.
Action
Add to Block ListAdds a single domain to a DNSFilter policy's block list, with a note explaining why.
Action
Allow Category in a PolicyAllows a content category in a DNSFilter policy by taking it off that policy's blocked-category list.
Action
Assign Policy to a Roaming ClientAssigns a DNSFilter policy to a roaming client, so that device filters against that policy.
Action
Assign Policy to a SiteAssigns a DNSFilter policy to a site, so traffic from that site filters against that policy.
Action
Block Category in a PolicyBlocks a content category in a DNSFilter policy by adding it to that policy's blocked-category list.
Action
Create SiteCreates a new site (network) in DNSFilter, optionally on a chosen policy and block page.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.