Integration
Connect eSignatures to Ngrok
When something happens in eSignatures, your agent does the next thing in Ngrok. 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 eSignatures and Ngrok 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 eSignatures can start in Ngrok
When Contract Signed in eSignatures
then Add API key in Ngrok
When Contract Withdrawn in eSignatures
then Add credential in Ngrok
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 Ngrok
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.
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.
Action
Add API key/api_keys
Action
Add credential/credentials - create a tunnel authtoken credential.
Action
Add IP policy/ip_policies
Action
Add IP policy rule/ip_policy_rules
Action
Get IP policy ruleFetches an IP policy rule by ID, including its CIDR range, allow/deny action and the IP policy it belongs to. An error occurs if the rule is not found.
Action
Get reserved domain/reserved_domains/{id}
Action
List API keys/api_keys
Action
List credentials/credentials
Action
List IP policies/ip_policies
Action
List reserved domains/reserved_domains (paginated with before_id/limit).
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 Ngrok
HubSpot to NgrokHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to NgrokSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to NgrokSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to NgrokGoogle Sheets
Gmail to NgrokGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NgrokGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
eSignatures and Ngrok, 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 Ngrok when something happens in eSignatures?
Any of Ngrok's 10 actions, including Add API key, Add credential, Add IP policy and Add IP policy rule. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ngrok to eSignatures?
Ngrok has no triggers in the catalog today, so automations start in eSignatures. If you need the other direction, ask: your agent reads Ngrok's API documentation and adds it.
Do I have to build a connector for eSignatures or Ngrok?
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.