Integration
Connect eSignatures to Landbot
When Contract Signed fires in eSignatures, your agent runs Send text message in Landbot. 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 Landbot 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 Landbot
When Contract Signed in eSignatures
then Send text message in Landbot
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 Landbot
Triggers and actions 4 triggers · 26 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.
- Archive customer
Archives a Landbot customer so their conversation moves out of the active inbox.
- Assign customer to agent
Assigns a Landbot customer conversation to a specific agent.
- Assign customer to bot
Assigns a Landbot customer to a bot, optionally starting the bot right away or from a specific node.
- Delete customer
Deletes a Landbot customer.
- Find customers by name, email or phone
Finds customers whose name, email or phone starts with the text you give. Returns up to 100 matching customers.
- Get channel
Returns a Landbot channel's details, including its name, type, active status and appearance settings.
- Get customer
Returns a Landbot customer's profile, including name, channel, assigned agent, archive status and custom field values.
- Get customer field
Returns the name, type and current value of one custom field stored on a Landbot customer.
- List channels
Returns the channels in your Landbot workspace, optionally filtered by type and active status.
- List customer messages
Returns the full conversation transcript for a Landbot customer — every message exchanged with them.
- List customers
Returns the customers in your Landbot workspace, optionally filtered by channel, assigned agent, archive or WhatsApp opt-in status, or a name/email/phone prefix.
- List WhatsApp templates
Returns the WhatsApp message templates available to send to customers, optionally limited to one channel.
- Send text message
Sends a text message to a Landbot customer on their channel.
- Send WhatsApp template
Sends an approved WhatsApp template message to a Landbot customer, filling in its placeholders. Use it to reach a customer outside WhatsApp's 24-hour messaging window.
- Update customer field
Changes the value of an existing custom field on a Landbot customer. The field must already exist on the customer.
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 Landbot
Gmail to LandbotGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
eSignatures and Landbot, 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 Landbot when something happens in eSignatures?
Any of Landbot's 15 actions, including Send text message, Send WhatsApp template, Update customer field and Assign customer to agent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Landbot to eSignatures?
Landbot has no triggers in the catalog today, so automations start in eSignatures. If you need the other direction, ask: your agent reads Landbot's API documentation and adds it.
Do I have to build a connector for eSignatures or Landbot?
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 Landbot 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.