Integration
Connect Doclift PDF and eSignatures
When something happens in Doclift PDF or eSignatures, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Doclift PDF and eSignatures to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Doclift PDF and eSignatures can do together
From Doclift PDF to eSignatures
When New PDF Document Generated in Doclift PDF
then Add Signer in eSignatures
When New PDF Document Generated in Doclift PDF
then Add Template in eSignatures
From eSignatures to Doclift PDF
When Contract Signed in eSignatures
then Add Template in Doclift PDF
When Contract Withdrawn in eSignatures
then Add Variable in Doclift PDF
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Doclift PDF and eSignatures
Triggers and actions 5 triggers · 22 actions
Trigger
New PDF Document GeneratedWebhook trigger for Doclift's async document-generation completion callback (POST .../webhooks/doclift, X-Doclift-Signature: sha256=hmac). Delivery URL is configured manually on the external application in the Doclift dashboard — no register/list/delete API exists. Fires once per document_request (all its documents_generations resolved to success/error), payload includes id, tag, type, timestamp, documents_generations[] (generation_status, file{filename,url,size}).
Action
Add Templatecreate a custom (HTML-body) template: title, description, content, orientation, margins, optional variables_attributes. Server forces category=custom.
Action
Add Variablecreate a variable on a custom template: title (unique, naming pattern), description, field_type (text/checkbox/radio/select/collection, default text), seed_value, allowed_values.
Action
Delete Templateremoves a custom template (scope restricted to category=custom, non-archived, same org).
Action
Get Document Requeststatus and documents_generations detail (signed file url, valid 2 hours) for one document request.
Action
Get Templatefull template detail including variables and content (custom templates); works for any published template of the three categories.
Action
List Document Requestslist document generation requests with id, tag, type, status, documents_generations (each with generation_status and file url).
Action
List Templatesreturns published, non-archived templates (custom/fillable_form/workflow) for the organization: id, title, description.
Action
List Variablesall variables of a custom, non-archived template: id, title, description, field_type, allowed_values (no pagination, no seed_value).
Action
Publish Templatemarks a custom template published (usable for document generation).
Action
Unpublish Templatemarks a custom template unpublished.
Action
Update Variableupdate description/field_type/allowed_values/title of a variable; allowed_values replaces the stored array.
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.
Action
Add TemplateCreate a new reusable contract template.
Action
Create ContractCreates a new contract.
Action
Delete SignerRemove a signer from a contract that has not yet signed.
Action
Delete TemplateDelete a contract template.
Action
Get ContractRetrieve a contract's current status, signer states, and metadata.
Action
Get TemplateRetrieve a contract template's details.
Action
List TemplatesList all contract templates in the account.
Action
Send Contract DraftSend a previously created draft contract to its signers.
Action
Update TemplateUpdate an existing contract template's title or settings.
Action
Withdraw ContractWithdraw (cancel) a contract that has been sent but not fully signed.
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
What our customers say
More from Doclift PDF
Doclift PDF to Dungeons and DragonsThe D&D 5th Edition API (dnd5eapi.co) is a public reference database for the Dungeons and Dragons 5e System...
Doclift PDF to FutureAGIFutureAGI is a platform for evaluating and optimizing AI systems to ensure performance, safety, and...
Doclift PDF to ItsThisForThatItsThisForThat generates random "X for Y" startup ideas — the classic mashup pitch format.
Doclift PDF to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Doclift PDF to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Doclift PDF to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into eSignatures
Gmail to eSignaturesGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Drive to eSignaturesGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to eSignaturesActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to eSignaturesOrganize anything with Airtable, a modern database created for everyone.
Asana to eSignaturesAsana is a collaborative information manager for workspace.
ClickUp to eSignaturesClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Questions
Doclift PDF and eSignatures, answered
What can start an automation from Doclift PDF?
Any of Doclift PDF's 1 trigger in the catalog, including New PDF Document Generated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in eSignatures when something happens in Doclift PDF?
Any of eSignatures's 11 actions, including Create Contract, Send Contract Draft, Update Template and Add Signer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from eSignatures to Doclift PDF?
Yes. When something happens in eSignatures, your agent can act in Doclift PDF too. This page covers both directions: eSignatures's triggers and Doclift PDF's actions are listed here as well.
Do I have to build a connector for Doclift PDF or eSignatures?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.