Integration
Connect Conversion Tools to eSignatures
When something happens in Conversion Tools, 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 Conversion Tools 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 Conversion Tools and eSignatures
Triggers and actions 8 triggers ยท 13 actions
Trigger
Conversion FailedTriggered when a file conversion fails, giving the reason it failed.
Trigger
Conversion Result AvailableTriggered when a finished conversion has its result file ready to download.
Trigger
Conversion StartedTriggered when a new file conversion is submitted, while it is still queued or running.
Trigger
Conversion Successfully FinishedTriggered when a file conversion finishes successfully.
Action
Convert FileUploads a file to Conversion Tools and starts converting it, returning the conversion ID. Use one of the result triggers or Convert File and Get the Result to pick up the converted file.
Action
Convert File and Get the ResultUploads a file to Conversion Tools, converts it, waits for the conversion to finish and returns a link to download the result.
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.