Integration

Connect Outlook to Google Cloud Run

When Calendar Event Changes fires in Outlook, your agent runs Get Service in Google Cloud Run. 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 Outlook and Google Cloud Run 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

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)

Connecting Outlook and Google Cloud Run lets mail and calendar events in Outlook stand in for a console. A request that lands in the inbox can start a Cloud Run job, a scheduled event can kick off the same job, and the reply with the execution status goes back out through Outlook. Each scenario is tested before it runs.

Example flows

What Outlook can start in Google Cloud Run

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 Outlook and Google Cloud Run

Triggers and actions 5 triggers ยท 49 actions

Each app on its own

Reviews

What our customers say

More from Outlook

More into Google Cloud Run

Questions

Outlook and Google Cloud Run, answered

Can something happening in Cloud Run start one of these flows?

No, Google Cloud Run has no triggers here, so every flow begins with an Outlook event such as a new message, a new or changed calendar event, or a new sent message. Cloud Run supplies the actions, like Run Job, Get Execution, Get Service, List Jobs, List Revisions and List Services.

How do I find out whether the job that was started actually finished?

Run Job returns an execution ID, and Get Execution reports how the tasks are doing, so the agent can read that and send the outcome back through Outlook as a reply or an email. The agent tests each scenario, including the case where the named job is not found.

What can start an automation from Outlook?

Any of Outlook's 5 triggers in the catalog, including Calendar Event Changes, New Calendar Event, New Contact Added and New Outlook Message. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Google Cloud Run when something happens in Outlook?

Any of Google Cloud Run's 6 actions, including Get Service, List Jobs, List Revisions and List Services. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Google Cloud Run to Outlook?

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

Do I have to build a connector for Outlook or Google Cloud Run?

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.