Claude Embat connectorWhat Claude can do in your Embat account.
The Claude Embat connector exposes 1 tool, and it reads. 1 read, 0 write, 0 undocumented: Claude puts your treasury questions to TellMe and answers with your own Embat figures. Here is what it sees, what it leaves alone, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
Treasury answers without opening the dashboard
A finance lead who wants today's cash position normally logs into Embat, picks the right view and filters it. With the connector, you type the question in Claude in plain English. Claude hands it to TellMe, in Embat, and builds its reply on the numbers TellMe sends back, limited to what your Embat account can already see.
A cash check before a meeting. Before a finance meeting, you ask for balances and debt positions. Claude calls ask_tellme and brings back Embat's figures.
A forecast sanity check. A controller wants to know what the treasury forecast says for the coming weeks. Same tool, different question: the figures come from Embat, Claude only phrases them.
Reconciliation questions in plain words. PSP reconciliations, payments and intercompany positions are all in scope according to the directory sheet, so an accountant can ask where a gap comes from without building a report first.
What it will not do: by default the sheet shows reading only. Nothing on it creates a payment, books an entry or changes a forecast, and nothing runs on a schedule. Claude only calls the tool while it is answering you. If you need a recurring export or an alert, that is the job of an automation platform; the Integrations hub lists the ones we cover.
Five words before you connect
The Claude vocabulary this page uses, in under a minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named job a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- Embat's own sign-in screen, where you give Claude the access it will use afterwards. Granted once per person, revocable.
- Approval
- The confirmation Claude waits for before it changes something in an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Embat.
Connect the Claude Embat connector in three steps
- 01
Find Embat in Claude
Open Claude's settings, go to Customize then Connectors, and look for Embat in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before any member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Embat in the window Embat opens itself. If the link breaks later, use Disconnect and connect again: that usually fixes it.
- 03
Read the authorization screen
Go through Embat's authorization screen before you accept. It belongs to Embat, not to Claude, and it is what decides how far the access reaches. You can also withdraw that access later from the Embat side.
The single tool, and what it reads
Embat gives Claude 1 tool: 1 that read your account, 0 that change something in it.
One tool, documented by the directory sheet itself. Its name stays exactly as Claude shows it.
- 1 read
What Claude reads (1)
1 toolOne tool that queries your treasury data and changes nothing.
ask_tellme
Passes your question, in everyday language, to TellMe and brings back an answer built on your real Embat numbers: cash, debt, forecasts, accounting, payments, PSP reconciliations or intercompany positions.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request appears in the conversation, right when it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked each time. They can also cap what a connector may do for the whole organization, for instance keep reading and close writing, and nobody overrides that from their own account. Claude works with your rights and nothing more: Embat states that TellMe inherits your existing permissions, so it never reaches further than you do.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, the answer is not published anywhere: it is a real gap in the catalogue.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member signs in. For this one's current status, check its sheet in the official directory. Note that only the directory sheet documents Embat: no Claude help article covers it.
Where this connector stops
A connector is not an automation. Claude calls ask_tellme while it answers you; nothing fires when a payment lands or a forecast moves.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic states on every sheet that it does not choose the tools a publisher exposes or guarantee they behave as described. Only connect what comes from a publisher you trust. No source says which Embat data, if any, stays outside TellMe's reach.
Need help connecting Embat to Claude?
A person reads every message.
