FlowsBook a callSign inCreate free accountSign up
AI employees and automation

How to use AI employees from ChatGPT, Claude and other AI assistants

Offer a live AI employee as a tool, connect your assistant once, and ask for it in a sentence: it runs as you, with your rights, and answers with what it found.

Part of the guide AI employees

By the xMap team · · 5 min read

You can use AI employees from ChatGPT, Claude and other assistants by offering a live AI employee as a tool and connecting the assistant to xMap Flows once. After that, a colleague who is already working in their assistant can say check this address for a bakery and the assistant calls your AI employee, which runs as that person, does its usual job on live data and hands back what it found. The employee is built, tested and owned in xMap Flows; the assistant is just another way to start it.

This suits teams where people spend their day in a chat assistant and do not want to open another app for every question. It covers what offering a tool means, how the assistant knows what to send, connecting each assistant, who can call what, and where it is the wrong fit. If AI employees are new to you, start with the overview.

What offering a tool means

An AI employee in xMap Flows is a flow with a job: it reads data, decides with AI and reports somewhere. Normally it runs on a timetable, when a form is filled in or when a message arrives. Offering it as a tool adds one more trigger: an assistant asking for it.

  1. Deploy the flow, so it is live.
  2. Open its ... menu and choose Offer as a tool to AI assistants, or use As a tool in the employee's panel.
  3. Check the tool name. It must be unique in your organization; assistants see it as employee_ followed by that name.
  4. Write one sentence on what it does and when to use it. Assistants read this sentence to decide whether your employee fits the request, so be specific: Checks a street address for a kind of shop: competitors within a short walk, residents nearby where population data exists, and road speeds.

Only the flow's owner or an organization admin can offer or withdraw it.

How the assistant knows what to send

An assistant fills in inputs, so your employee needs clear ones. xMap Flows works them out from the flow itself, in this order:

  • the fields of its Form page, with their kinds (text, number, email, a choice, a place, a date) and which are required;
  • else the fields its Webhook start lists;
  • else its variables;
  • else a single request in plain words.

A Form page with three well-named fields, such as Address, Kind of business and Walking distance, gives the best results, because the assistant knows exactly what to collect and the same form also works for people who prefer a web page.

Connecting the assistant

Each person connects their own assistant to the xMap Flows MCP server at https://flows.xmap.ai/mcp:

AssistantHow it connectsKey needed?
ClaudeSettings, Connectors, add a custom connector with that address, then sign in and press AllowNo
ChatGPTA connector in developer mode with that address and OAuth, then sign in and press AllowNo
Claude Code, Cursor and othersA personal access key made under Settings, API keys and AI assistantsYes

On team plans of an assistant, its own admin may need to allow connectors first.

Once connected, the offered employees appear among the assistant's tools alongside the general xMap Flows tools. Connected assistants are listed under Settings, API keys and AI assistants, and deleting one disconnects it at once.

Who can call it, and what happens

  • Only people who may run the flow can call it, and only from organizations their sign-in opens.
  • Read-only access keys cannot call an employee, since a call is a run.
  • Each call is a real run as the caller. If the flow has Send for real on, the run may send its emails or messages exactly as a scheduled run would.
  • Calls use your organization's credits and count toward the flow's monthly budget.
  • Short jobs answer within about 45 seconds with up to 100 items. Longer ones reply that the run is still going, and the assistant can check its result later.
  • Every call shows in the flow's runs and on Activity, with who called it.

A made-up example

A small retail property consultancy in Vancouver has an AI employee called Site checker. It has a Form page with Address and Kind of business, then Area of interest, Nearby places for competitors within 500 m, Demographics for who lives within a kilometre (Canada has population data), and an xMap LLM block that writes a five-line verdict. Send for real is off, so it only reports.

An analyst is drafting a client note in Claude and types: Use the site checker on 1100 Robson Street for a bakery, and put the verdict in my note. Claude fills Address and Kind of business, calls the employee, waits for the answer and writes the verdict into the draft with the count of nearby bakeries it was given. The run sits in the flow's history like any other, so the analyst's manager can open exactly what was checked.

When this is the wrong fit

  • Jobs that should run on their own. A morning lead list belongs on a schedule, not on someone remembering to ask.
  • Employees that hold conversations. A chat page agent already talks to people; calling it from another assistant adds a layer for no gain.
  • Anything that needs a person to approve first. Keep approvals in the flow, where the approver gets the request, rather than relying on the assistant to ask.
  • Vague tool sentences. If two offered employees sound alike, the assistant may pick the wrong one. Rename or reword until each is clearly different.

Questions

Do I need to rebuild my AI employee to use it from ChatGPT or Claude?

No. Any live flow can be offered as a tool from its ... menu. Adding a Form page with clear fields makes the inputs easier for assistants to fill.

Can a colleague call an employee they cannot see in xMap Flows?

No. Only people who may run the flow can call it, and the assistant only sees employees in the organizations their sign-in opens.

Will a call from an assistant send emails?

Only if the flow has Send for real switched on, in which case it behaves exactly like a scheduled run. Keep it off for employees that should only report back.

Does the assistant see all my data?

It sees what the employee returns for that call, plus what the general xMap Flows tools let that person see. Its access is never wider than the person's own.

How do I stop offering an employee?

Switch it off in the same Offer as a tool window, or pause the flow. Assistants no longer list it.

Templates that do this

Read next

More on ai employees and automation · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.