Integration
Connect CloudConvert and eSignatures
When Job Failed fires in CloudConvert, your agent runs Add Signer in eSignatures, or Contract Signed in eSignatures to Convert a File in CloudConvert. Describe the whole flow 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 CloudConvert and eSignatures to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 CloudConvert and eSignatures can do together
From CloudConvert to eSignatures
When Job Failed in CloudConvert
then Add Signer in eSignatures
When Job Finished in CloudConvert
then Add Template in eSignatures
From eSignatures to CloudConvert
When Contract Signed in eSignatures
then Convert a File in CloudConvert
When Contract Withdrawn in eSignatures
then Get file metadata in CloudConvert
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 CloudConvert and eSignatures
Triggers and actions 6 triggers · 15 actions
Trigger
Job FailedTriggers when a job failed.
Trigger
Job FinishedTriggers when a job finished.
Action
Capture a WebsiteCreates job to capture a website as PDF or create a website screenshot as JPG or PNG.
Action
Convert a FileCreates job to convert a file.
Action
Get file metadataExtract metadata (e.g. page count, dimensions, duration) from a file (metadata operation task).
Action
Get jobLook up the status and results of a conversion job by ID.
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 CloudConvert
CloudConvert to Earnings FeedReal-time SEC filings, insider trades, and institutional holdings
CloudConvert to Google GeminiGoogle AI Studio is a fast, easy way to start prototyping generative AI ideas using Google's Gemini model.
CloudConvert to Open Government, Queensland GovernmentQueensland Government Open Data. Public open-data portal — search dataset catalogs and retrieve published...
CloudConvert to Studio GhibliThe Studio Ghibli API is a public catalogue of the people, places and things from the Studio Ghibli film...
CloudConvert to TrengoTrengo is a team collaboration tool to manage conversations from channels such as web chat, email and...
CloudConvert to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
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
CloudConvert and eSignatures, answered
What can start an automation from CloudConvert?
Any of CloudConvert's 2 triggers in the catalog, including Job Failed and Job Finished. Describe the moment in plain language and your agent picks the right one.
What can your agent do in eSignatures when something happens in CloudConvert?
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 CloudConvert?
Yes. When something happens in eSignatures, your agent can act in CloudConvert too. This page covers both directions: eSignatures's triggers and CloudConvert's actions are listed here as well.
Do I have to build a connector for CloudConvert 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.
Can my AI client use CloudConvert and eSignatures without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.