Integration
Connect Foxit eSign to NameAPI
When Document Cancelled fires in Foxit eSign, your agent runs Detect contact risk in NameAPI. 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 Foxit eSign and NameAPI 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 Foxit eSign can start in NameAPI
When Document Cancelled in Foxit eSign
then Detect contact risk in NameAPI
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 Foxit eSign and NameAPI
Triggers and actions 2 triggers · 12 actions
- Document Cancelled
Triggers when a recipient cancels or declines a Foxit eSign envelope (folder).
- Document Deleted
Triggers when a Foxit eSign envelope (folder) is deleted.
- Add folder from PDFs
Creates a folder of documents for signature from PDF files at public URLs or in base64, with its recipient parties, and optionally sends it right away or opens embedded sending/signing sessions.
- Cancel folder
Cancels a sent folder (envelope) so recipients can no longer sign its documents, recording the reason in the folder's history.
- Find folders by status and date
Returns the IDs of folders (envelopes) created within a date range, optionally filtered by status such as executed, sent or draft.
- Get folder
Returns the full details of a Foxit eSign folder (envelope), including its status, documents and recipient parties.
- Send signature reminder
Sends a reminder email to the recipients of a folder (envelope) who have not yet signed it.
- Detect contact risk
Risk Detector: scores a person/email/address record for fake or risky data.
- Detect disposable email address
Disposable Email Address Detector: checks whether an email is disposable.
- Format person name
Name Formatter: formats a person name (e.g. salutation/full name) per locale.
- Genderize person name
Name Genderizer: infers gender from a person name.
- Match person names
Name Matcher: compares two person names and returns a match type/confidence.
- Parse email name
Email Name Parser: extracts a person name from an email address.
- Parse person name
Name Parser: splits a full name into components (given/family names, title, gender).
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 Foxit eSign
Foxit eSign to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Foxit eSign to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Foxit eSign to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Foxit eSign to Google SheetsGoogle Sheets
Foxit eSign to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Foxit eSign to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into NameAPI
Questions
Foxit eSign and NameAPI, answered
What can start an automation from Foxit eSign?
Any of Foxit eSign's 2 triggers in the catalog, including Document Cancelled and Document Deleted. Describe the moment in plain language and your agent picks the right one.
What can your agent do in NameAPI when something happens in Foxit eSign?
Any of NameAPI's 7 actions, including Detect contact risk, Detect disposable email address, Format person name and Genderize person name. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from NameAPI to Foxit eSign?
NameAPI has no triggers in the catalog today, so automations start in Foxit eSign. If you need the other direction, ask: your agent reads NameAPI's API documentation and adds it.
Do I have to build a connector for Foxit eSign or NameAPI?
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.