Integration
Connect Hero Parser to eSignatures
When something happens in Hero Parser, your agent does the next thing in eSignatures. 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 eSignatures 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 eSignatures
Triggers and actions 6 triggers ยท 23 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
Contract SignedTriggers when a contract is signed by all signers.
Trigger
Contract WithdrawnFires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn".
Trigger
Signer Declined SignatureFires when a signer declines to sign the contract. Webhook event "Signer declined the signature".
Trigger
Signer Viewed ContractFires when a signer opens/views the contract. Webhook event "Signer viewed the contract".
Action
Add SignerAdd a new signer to an existing contract. POST /api/contracts/:id/signers (Contracts - Signers - Add).
Action
Add TemplateCreate a new reusable contract template. POST /api/templates (Templates - New).
Action
Create ContractCreates a new contract.
Action
Delete SignerRemove a signer from a contract that has not yet signed. DELETE /api/contracts/:id/signers/:signer_id (Contracts - Signers - Delete).
Action
Delete TemplateDelete a contract template. DELETE /api/templates/:id (Templates - Delete).
Action
Get ContractRetrieve a contract's current status, signer states, and metadata. GET /api/contracts/:id (Contracts - Query).
Action
Get TemplateRetrieve a contract template's details. GET /api/templates/:id (Templates - Query).
Action
List TemplatesList all contract templates in the account. GET /api/templates (Templates - List).
Action
Send Contract DraftSend a previously created draft contract to its signers. POST /api/contracts/:id/send (Contracts - Send draft).
Action
Update TemplateUpdate an existing contract template's title or settings. PUT /api/templates/:id (Templates - Update).
Action
Withdraw ContractWithdraw (cancel) a contract that has been sent but not fully signed. POST /api/contracts/:id/withdraw (Contracts - Withdraw).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.