Integration

Connect Google Calendar to ip-api

When Attendee Response Changed fires in Google Calendar, your agent runs Get IP geolocation in ip-api. 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 Google Calendar and ip-api to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start 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)

Google Calendar holds the events, and ip-api turns an IP address or domain into a city, timezone, ISP and network owner. Joining them lets a team read the IP or hostname sitting in an event's description or location, resolve it with ip-api, and write the result back onto the Google Calendar event before the meeting starts.

Example flows

What Google Calendar can start in ip-api

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 Google Calendar and ip-api

Triggers and actions 6 triggers · 47 actions

Each app on its own

Reviews

What our customers say

More from Google Calendar

More into ip-api

Questions

Google Calendar and ip-api, answered

Where does the IP address or domain come from?

It comes from the Google Calendar event itself, usually an IP or hostname your booking form or dial-in details left in the description or location field. The agent reads that value from the trigger data and passes it to the ip-api lookup.

Can ip-api start a workflow on its own?

No, ip-api only answers lookups, so every scenario here begins with a Google Calendar trigger such as an event being created, updated, synced, starting soon, or an attendee changing their RSVP. The agent builds it, tests each scenario, and keeps it running.

What can start an automation from Google Calendar?

Any of Google Calendar's 6 triggers in the catalog, including Attendee Response Changed, Calendar Event Sync, Event Created and Event Starting Soon. Describe the moment in plain language and your agent picks the right one.

What can your agent do in ip-api when something happens in Google Calendar?

Any of ip-api's 2 actions, including Get IP geolocation and Get IP geolocations (batch). Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from ip-api to Google Calendar?

ip-api has no triggers in the catalog today, so automations start in Google Calendar. If you need the other direction, ask: your agent reads ip-api's API documentation and adds it.

Do I have to build a connector for Google Calendar or ip-api?

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 Google Calendar and ip-api 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.