Integration
Connect CallFire to IP2Location
When New call fires in CallFire, 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 CallFire 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)Example flows
What CallFire can start in IP2Location
When New call in CallFire
then Get my IP details in IP2Location
When New contact in CallFire
then Lookup domain WHOIS 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 CallFire and IP2Location
Triggers and actions 4 triggers · 13 actions
Trigger
New callPolls for completed calls. Fires for each new inbound or outbound call.
Trigger
New contactPolls for newly created contacts in the account.
Trigger
New SMS text receivedPolls for inbound SMS text messages. Fires for each newly received text.
Trigger
New text sentPolls for outbound SMS text messages. Fires for each newly sent text.
Action
Add new contactCreates a new contact in CallFire and returns its ID.
Action
Delete contactDeletes a contact by its CallFire contact ID.
Action
Get contact by IDRetrieves a single contact by its CallFire contact ID.
Action
Get contact by propertyGet contact details by property name and value.
Action
Get text messageRetrieves a single sent or received text message by its ID.
Action
List contact listsReturns all contact lists in the account.
Action
Remove contact from listRemoves a contact (by contact ID) from a specified contact list.
Action
Send SMS text messageSends an SMS text message to one phone number and returns the new text's ID and state.
Action
Send voice callPlaces a text-to-speech voice call to one phone number and returns the new call's ID and state.
Action
Update contactUpdates an existing contact by its CallFire contact ID.
Action
Get my IP detailsReturns geolocation details for the IP address the request originates from. Takes no IP argument.
Action
Lookup domain WHOISLook up WHOIS registration details for a domain via the IP2WHOIS API (registrar, dates, registrant, nameservers).
Action
Lookup IP geolocationLook 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 CallFire
CallFire to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CallFire to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CallFire to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CallFire to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
CallFire to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CallFire to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into IP2Location
Slack to IP2LocationSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Stripe to IP2LocationStripe is a payment processing platform for online businesses.
Shopify to IP2LocationShopify is a commerce platform for online stores and retail point-of-sale.
Pipedrive to IP2LocationPipedrive is a sales CRM and pipeline management tool.
Trello to IP2LocationTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Asana to IP2LocationAsana is a collaborative information manager for workspace.
Questions
CallFire and IP2Location, answered
What can start an automation from CallFire?
Any of CallFire's 4 triggers in the catalog, including New call, New contact, New SMS text received and New text sent. Describe the moment in plain language and your agent picks the right one.
What can your agent do in IP2Location when something happens in CallFire?
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 CallFire?
IP2Location has no triggers in the catalog today, so automations start in CallFire. 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 CallFire 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 CallFire 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.