Integration
Connect HelloSign to IP2Location
When New Signature Request fires in HelloSign, your agent runs Get my IP details in IP2Location. 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 IP2Location 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)HelloSign tells you when a signature request goes out and who is signing it; IP2Location tells you where an address sits, what network it belongs to, and whether a domain's registration checks out. Joined together, each new request in HelloSign can carry a location and WHOIS check alongside it, and requests that look wrong can be cancelled before anyone signs.
Example flows
What HelloSign can start in IP2Location
When New Signature Request in HelloSign
then Get my IP details in IP2Location
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 IP2Location
Triggers and actions 1 trigger · 11 actions
- New Signature Request
Triggers when a new signature request appears in the account.
- Cancel Signature Request
Cancels an incomplete signature request.
- Get Account
Returns information about the current Dropbox Sign account.
- Get Signature Request
Retrieves a single signature request by its ID.
- Get Signature Request Files
Returns a download URL for the documents of a signature request as a PDF.
- List Signature Requests
Lists signature requests for the account, paginated and ordered newest first.
- List Templates
Lists the reusable templates available to the account.
- Send Reminder
Sends an email reminder to a signer to sign a pending signature request.
- Send Signature Request
Creates and sends a new signature request using document file URLs and a list of signers.
- Get my IP details
Returns geolocation details for the IP address the request originates from. Takes no IP argument.
- Lookup domain WHOIS
Look up WHOIS registration details for a domain via the IP2WHOIS API (registrar, dates, registrant, nameservers).
- Lookup IP geolocation
Look up full geolocation, network, proxy and security details for an IP address (IPv4 or IPv6).
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 IP2Location
Stripe to IP2LocationStripe is a payment processing platform for online businesses.
Pipedrive to IP2LocationPipedrive is a sales CRM and pipeline management tool.
Asana to IP2LocationAsana is a collaborative information manager for workspace.
Questions
HelloSign and IP2Location, answered
Can a signature request be cancelled based on what IP2Location returns?
Yes. The agent can read the full request with Get Signature Request, run Lookup IP geolocation, and call Cancel Signature Request in HelloSign when the lookup flags the address as a proxy, and it tests every scenario before the setup goes live.
Does IP2Location ever start the automation?
No, IP2Location has no triggers, so every run begins with a new signature request in HelloSign. From there the agent can call Lookup IP geolocation, Lookup domain WHOIS or Get my IP details and pass the result back into your HelloSign steps.
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 IP2Location when something happens in HelloSign?
Any of IP2Location's 3 actions, including Get my IP details, Lookup domain WHOIS and Lookup IP geolocation. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from IP2Location to HelloSign?
IP2Location has no triggers in the catalog today, so automations start in HelloSign. If you need the other direction, ask: your agent reads IP2Location's API documentation and adds it.
Do I have to build a connector for HelloSign or IP2Location?
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 HelloSign and IP2Location 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.