Integration
Connect eSignatures to Zamzar
When something happens in eSignatures, your agent does the next thing in Zamzar. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want eSignatures and Zamzar 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 eSignatures and Zamzar
Triggers and actions 6 triggers ยท 20 actions
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).
Trigger
New Conversion JobTriggered when a new conversion job is created in your Zamzar account.
Trigger
New FileTriggered when a new file appears in your Zamzar account, whether uploaded or produced by a conversion.
Action
Convert FileStarts a Zamzar conversion job that converts a file you supply into another format. Returns the new job with its id and status so you can check on it or collect the converted file later.
Action
Create Content FileCreates a file on Zamzar from text content you supply, so it can be converted or downloaded later. Returns the stored file with its id, name and size.
Action
Delete conversion jobDeletes a conversion job from Zamzar. Returns the job that was removed.
Action
Delete fileDeletes a file stored on Zamzar. Returns the file that was removed.
Action
Find Converted FileLooks through the files stored on Zamzar and returns the ones whose name matches the text you supply. Use it to locate a converted file after a conversion job has finished.
Action
Get conversion jobReturns a single Zamzar conversion job, including its current status and any converted files it produced.
Action
Get fileReturns the details of a single file stored on Zamzar, including its name, format and size.
Action
List conversion jobsReturns the conversion jobs in your Zamzar account, most recent first.
Action
List formatsReturns every source format Zamzar can convert from, along with the target formats each one can be converted into.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.