Integration
Connect eSignatures to FilePost
When something happens in eSignatures, your agent does the next thing in FilePost. 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 FilePost 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 FilePost
Triggers and actions 4 triggers · 21 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).
Action
Create Intake LinkCreates a FilePost intake link — a public upload page you can send to someone so they can drop files to you, with your own limits on file type, size, count and how long it stays open.
Action
Delete FilePermanently deletes a file from FilePost. The stored file and its public link are removed and cannot be recovered.
Action
Delete intake linkCloses a FilePost intake link so it stops accepting uploads. Files already uploaded through it are untouched, and the slot frees up against your plan's limit on active links.
Action
Get fileReturns the details FilePost holds about one stored file — its name, size, type, download link and when it expires.
Action
Get intake linkReturns one intake link from your FilePost account, looked up by its intake link ID. FilePost has no single-link endpoint, so the link is selected out of your full list of intake links.
Action
List FilesReturns the files stored in your FilePost account, newest first, together with the total number of files.
Action
List intake linksReturns the intake links on your FilePost account, with each link's label, public upload page, limits and expiry.
Action
Update fileChanges whether a stored file's name appears in its public link, and returns the file with its new link.
Action
Upload FileUploads a file to FilePost and returns its shareable link.
Action
Upload File From URLStores a file from a public web link in FilePost and returns its shareable link.
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