Integration
Connect HelloSign to Base64.ai
When New Signature Request fires in HelloSign, your agent runs Match signatures in Base64.ai. 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 HelloSign and Base64.ai 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 HelloSign can start in Base64.ai
When New Signature Request in HelloSign
then Match signatures in Base64.ai
When New Signature Request in HelloSign
then Scan a Document by Bytes in Base64.ai
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 HelloSign and Base64.ai
Triggers and actions 1 trigger · 12 actions
Trigger
New Signature RequestTriggers when a new signature request appears in the account.
Action
Cancel Signature RequestCancels an incomplete signature request.
Action
Get AccountReturns information about the current Dropbox Sign account.
Action
Get Signature RequestRetrieves a single signature request by its ID.
Action
Get Signature Request FilesReturns a download URL for the documents of a signature request as a PDF.
Action
List Signature RequestsLists signature requests for the account, paginated and ordered newest first.
Action
List TemplatesLists the reusable templates available to the account.
Action
Send ReminderSends an email reminder to a signer to sign a pending signature request.
Action
Send Signature RequestCreates and sends a new signature request using document file URLs and a list of signers.
Action
Match faces/api/face. With one document, detects faces; with document (ground truth) plus query (e.g. selfie), returns matching face coordinates. Accepts base64 data URI or url.
Action
Match signatures/api/signature. With one document, detects signatures; with document (ground truth) plus query, verifies whether the signatures match. Accepts base64 data URI or url.
Action
Scan a Document by BytesScans a document that is provided by a string of bytes (e.g. data:image/png;base64,iVBORw0KGgoAAAANSUhEU...). File can be an image (jpeg, png etc.), PDF, zip or an office document (.doc, .docx, etc.).
Action
Scan a Document by URLScans a document that is provided by a URL or Hydrate File. File can be an image (jpeg, png etc.), PDF, zip or an office document (.doc, .docx, etc.).
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 HelloSign
HelloSign to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
HelloSign to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
HelloSign to MailchimpMailchimp marketing automation and email platform.
HelloSign to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
HelloSign to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
HelloSign to JIRAAtlassian JIRA Cloud — issue tracking and project management.
More into Base64.ai
HubSpot to Base64.aiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Base64.aiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Base64.aiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Base64.aiGoogle Sheets
Gmail to Base64.aiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Base64.aiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
HelloSign and Base64.ai, answered
What can start an automation from HelloSign?
Any of HelloSign's 1 trigger in the catalog, including New Signature Request. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Base64.ai when something happens in HelloSign?
Any of Base64.ai's 4 actions, including Match faces, Match signatures, Scan a Document by Bytes and Scan a Document by URL. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Base64.ai to HelloSign?
Base64.ai has no triggers in the catalog today, so automations start in HelloSign. If you need the other direction, ask: your agent reads Base64.ai's API documentation and adds it.
Do I have to build a connector for HelloSign or Base64.ai?
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.