Connecting Workiom to Your AI Assistant Using MCP

At a glance

• What this does: connects your Workiom workspace to an AI assistant over MCP
• Who can do this: anyone with a Workiom account, on every Workiom plan
• You need: an assistant that supports MCP, such as Claude or ChatGPT, on one of that assistant's paid plans
• Time: about three minutes, once
• Want to build Interfaces too? See Adding the Workiom Plugin for Interfaces

Connect Workiom to your AI assistant and you can ask it which clients have not been contacted in thirty days, and get the answer from your real data. The Workiom MCP gives your assistant a direct line into your workspace, so it can read your lists, create and update records, and upload files, all using the access you give it and nothing more.

MCP is an open standard for connecting assistants to the tools and data they work with. Workiom speaks it, so the same address and the same API key work with any assistant that supports it, including Claude and ChatGPT. The walkthrough below uses Claude as the example, but the setup is the same everywhere. Contact us if you want guidance for a specific assistant.

This article covers the connection on its own. If you also want to build Interfaces, which are custom pages that run inside your workspace, install the plugin instead. The plugin includes this same connection, so you do not need to do both.

What you can do once it is connected

• Ask questions about your own data in plain language, such as which clients have not been contacted in thirty days
• Have your assistant create, update or clean up records instead of doing it row by row
• Keep everything inside your own account, since the connection works through your key and your permissions

Before you start

You need your Workiom account and an assistant that supports MCP on one of its paid plans. Every Workiom plan includes the connection.

You will also need this address during the setup, so keep it handy:

https://mcp.workiom.com/mcp

Follow the walkthrough

Everything is in the walkthrough below. Step through it at your own pace and it will take you from an empty settings screen to a working connection. It is recorded in Claude, so the screens you see are Claude's. If you use a different assistant, the steps are the same and only the menu names change.

What it takes you through

1. Opening your assistant's settings
2. Adding the Workiom connector using the address above
3. Creating an API key in Workiom, under Workspace Settings, then Developer, then Integrations
4. Pasting that key into the authorization screen
5. Confirming the connection shows as connected

Two things to know while you follow it

Your API key is shown only once. Copy it before you close that window. If you lose it, you create a new one rather than looking it up.

You are granting three things on the authorization screen. Reading your Workiom data, creating, updating and deleting records, and uploading files on your behalf. Nothing outside your own workspace, and nothing you cannot revoke later.

Test it

Start a new chat and ask:

"List the applications in my Workiom workspace."

You should get your real applications back. From there you can go further, for example asking for every record in a list created this month grouped by source, or asking it to create a record from something you just described.

Three prompts to try

Once the test works, try the one that matches your team. Change the list names to match your own workspace.

Sales: "Which deals in my Deals list have not changed stage in the last 14 days? Group them by owner and show the total value."

Support: "Summarize this week's tickets in my Tickets list by category, and add a follow-up task to my Tasks list for every high-priority ticket that has no assignee."

Operations: "In my Assets list, find every asset with a maintenance date in the next 30 days, and add a reminder task for each one to my Tasks list."

If something does not work

Your assistant cannot find your workspace. Check your connectors list shows Workiom as connected rather than showing a Connect button. If the status looks stale, refresh the settings window.

Authorization failed. The key was probably copied incompletely, or it has been deleted in Workiom. Create a fresh key and authorize again.

You want to cut off access. Delete the API key in Workiom under Workspace Settings, then Developer, then Integrations. Access stops immediately, with nothing to change on the assistant side.

A note on safety

Your assistant only reaches Workiom through the key you created, so it inherits your permissions and nothing more. It cannot see other workspaces, and it cannot see anything you do not have access to yourself. If someone else on your team wants the same thing, they create their own key from their own account.

What comes next

With the connection in place, the next step for most teams is building something on top of it. Interfaces are custom pages that live inside your Workiom workspace, built by describing what you want. That needs the plugin, covered in Adding the Workiom Plugin for Interfaces.