Integration

Connect Google Docs to Raider

When something happens in Google Docs, your agent does the next thing in Raider. Describe it 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 Docs and Raider 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)

Raider.IO has the numbers your raid team argues about, and Google Docs is where the notes live. Connecting them means a doc can pull a character's Mythic+ score, a guild roster, the week's affixes or raid rankings from Raider and write them straight into the page you already keep. No credentials are needed on the Raider side.

Example flows

What Google Docs can start in Raider

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 Docs and Raider

Triggers and actions 10 triggers · 46 actions

Each app on its own

Reviews

What our customers say

More from Google Docs

More into Raider

Questions

Google Docs and Raider, answered

Can something in Raider start one of these?

No, Raider only offers lookups, so every run starts from a Google Docs event such as a new document, an update, a keyword appearing or a filled placeholder. Raider is then read for character, guild, run, affix or ranking details.

Can the results be written back into the same Google Doc?

Yes. After reading from Raider, the agent can use Insert Text Action, Replace All Text or Update Existing Document to put scores, rankings or affixes into the doc. The solution line on this page does exactly that.

What can start an automation from Google Docs?

Any of Google Docs's 10 triggers in the catalog, including Document Placeholder Filled, Document Search Update, Document Updated and Keyword Detected in Document. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Raider when something happens in Google Docs?

Any of Raider's 16 actions, including Find mythic+ runs, Get character profile, Get guild profile and Get mythic+ affixes. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Raider to Google Docs?

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

Do I have to build a connector for Google Docs or Raider?

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.