Integration
Connect eSignatures to Pexafy
When Contract Signed fires in eSignatures, your agent runs Delete collection in Pexafy. 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 Pexafy 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)Connecting eSignatures and Pexafy lets the paperwork side of a client project drive the image side. When a contract is signed, declined, viewed or withdrawn in eSignatures, the agent can create or clean up a Pexafy collection, search for photos by text, or look up a photographer profile, using details read straight off the contract.
Example flows
What eSignatures can start in Pexafy
When Contract Signed in eSignatures
then Delete collection in Pexafy
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 Pexafy
Triggers and actions 4 triggers · 24 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 collection
Create a new photo collection.
- Add photo to collection
Add a photo to a collection.
- Delete collection
Delete a collection by id.
- Delete photo from collection
Remove a photo from a collection.
- Find photographers by name
Search/suggest photographers by name.
- Find photos by image
Reverse image search: find photos visually similar to an uploaded image.
- Find photos by text
Search photos by keyword/text query.
- Find similar photos
Find photos visually similar to a given photo id.
- Get collection
Retrieve a collection by id.
- Get photo
Retrieve a single photo by id.
- Get photographer profile
Retrieve a photographer's profile by username.
- Get usage
Get current month API usage totals.
- List collections
List the account's photo collections.
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 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
eSignatures to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
eSignatures to MailchimpMailchimp marketing automation and email platform.
More into Pexafy
FastMode to PexafyFastMode is an AI-native CMS that takes AI-built websites from rough draft to live, fully editable, and...
Gmail to PexafyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
eSignatures and Pexafy, answered
Can the agent use details from the signed contract when searching Pexafy?
Yes. The agent can run Get Contract in eSignatures to read the signer names, status and metadata, then pass a project name or keyword into Find photos by text or use it to name a new Pexafy collection.
What happens in Pexafy if a contract never gets signed?
The Contract Withdrawn and Signer Declined Signature triggers in eSignatures can both drive Pexafy work, such as deleting the collection that was set up for that client or retrieving it first for review. The agent tests every scenario before it goes live.
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 Pexafy when something happens in eSignatures?
Any of Pexafy's 13 actions, including Delete collection, Find photos by text, Get collection and Get photographer profile. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pexafy to eSignatures?
Pexafy has no triggers in the catalog today, so automations start in eSignatures. If you need the other direction, ask: your agent reads Pexafy's API documentation and adds it.
Do I have to build a connector for eSignatures or Pexafy?
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 Pexafy 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.