Integration
Connect eSignatures to Daytona
When Contract Signed fires in eSignatures, your agent runs Add sandbox in Daytona. 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 eSignatures and Daytona 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 eSignatures can start in Daytona
When Contract Signed in eSignatures
then Add sandbox in Daytona
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 eSignatures and Daytona
Triggers and actions 4 triggers · 27 actions
- Contract Signed
Triggers when a contract is signed by all signers.
- Contract Withdrawn
Fires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn".
- Signer Declined Signature
Fires when a signer declines to sign the contract. Webhook event "Signer declined the signature".
- Signer Viewed Contract
Fires when a signer opens/views the contract. Webhook event "Signer viewed the contract".
- Add Signer
Add a new signer to an existing contract.
- Add Template
Create a new reusable contract template.
- Create Contract
Creates a new contract.
- Delete Signer
Remove a signer from a contract that has not yet signed.
- Delete Template
Delete a contract template.
- Get Contract
Retrieve a contract's current status, signer states, and metadata.
- Get Template
Retrieve a contract template's details.
- List Templates
List all contract templates in the account.
- Send Contract Draft
Send a previously created draft contract to its signers.
- Update Template
Update an existing contract template's title or settings.
- Withdraw Contract
Withdraw (cancel) a contract that has been sent but not fully signed.
- Add sandbox
Creates a new Daytona sandbox from a snapshot or build definition, with optional resources, labels, environment variables and network settings.
- Add snapshot
Creates a new snapshot from a container image or Dockerfile, which sandboxes can then be started from.
- Add volume
Creates a new storage volume in your Daytona organization that sandboxes can mount.
- Archive sandbox
Archives a stopped sandbox, moving its filesystem to cheaper storage until it is started again.
- Delete sandbox
Deletes a Daytona sandbox by its ID or name and returns the sandbox record as it is being destroyed.
- Delete snapshot
Deletes a snapshot from your Daytona organization.
- Delete volume
Deletes a Daytona volume. The volume must not be in use by any sandbox.
- Get sandbox
Returns the details of a sandbox, including its state, resources, labels and settings.
- Get snapshot
Returns a snapshot's details, including its state, image, resources and regions, looked up by ID or name.
- Get volume
Returns the details of a volume, including its name, state and timestamps.
- List sandboxes
Returns the sandboxes in your Daytona organization, optionally filtered by name, ID, labels, state, snapshot, region, class, resources, public status and dates, and sorted.
- List snapshots
Returns the snapshots in your Daytona organization, optionally filtered by name or by the sandbox they were created from.
- List volumes
Returns all volumes in your Daytona organization, optionally including deleted ones.
- Start sandbox
Starts a stopped or archived sandbox, or resumes a paused one, and returns the sandbox.
- Stop sandbox
Stops a running sandbox, optionally forcing it to shut down immediately. Returns the sandbox record.
- Update sandbox labels
Replaces all labels on a Daytona sandbox with the key-value pairs you supply.
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 eSignatures
eSignatures to PexafySemantic image search across 9+ free stock photo sources with a unified JSON schema
eSignatures to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
eSignatures to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
eSignatures to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
eSignatures to Google SheetsGoogle Sheets
eSignatures to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Daytona
Gmail to DaytonaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
eSignatures and Daytona, answered
What can start an automation from eSignatures?
Any of eSignatures's 4 triggers in the catalog, including Contract Signed, Contract Withdrawn, Signer Declined Signature and Signer Viewed Contract. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Daytona when something happens in eSignatures?
Any of Daytona's 16 actions, including Update sandbox labels, Add sandbox, Add snapshot and Add volume. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Daytona to eSignatures?
Daytona has no triggers in the catalog today, so automations start in eSignatures. If you need the other direction, ask: your agent reads Daytona's API documentation and adds it.
Do I have to build a connector for eSignatures or Daytona?
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 eSignatures and Daytona 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.