Claude Fyxer connectorWhat Claude can do in your Fyxer account.
The Claude Fyxer connector exposes 8 tools. 5 read your mail, meetings and contacts, 1 writes an email draft inside the chat, and 2 appear on the directory sheet with no official description. Here is what it reads, what it drafts, and what it never sends.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Fyxer account
Instead of digging through threads and call notes yourself, you ask Claude a plain question and it looks across the inbox and meetings Fyxer already holds for you. It can then write a reply in your style. The draft stays in the conversation: you decide whether it ever reaches your mailbox, and you press send yourself.
Find the decision nobody wrote down. An account manager asks what was agreed with a client last month; Claude runs search_context across emails, meetings and documents and brings back the passages that matter.
Catch up on a call you missed. Claude locates the session with search_meetings, then opens its summary through get_meeting or the full transcript with speaker notes through get_transcript.
Answer without starting from a blank page. With resolve_person Claude finds the right address, and draft_email writes the follow-up in your tone, ready for you to open in Outlook or Gmail.
What it will not do: Fyxer states plainly that no email leaves on your behalf, and nothing runs on its own when a message lands. Claude only acts while it answers you. Two tools, find_recordings and get_recording, are listed by the directory but described nowhere, so this page does not guess what they do. Recurring jobs that fire on every new email belong to an automation platform; the Integrations hub lists the ones we cover.
Five words before you connect
The Claude vocabulary around this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while answering you.
- Tool
- One named capability the connector opens to Claude. Claude chooses the ones it needs by itself; the directory lists them by name.
- Authorization
- Fyxer's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can revoke it.
- Approval
- The confirmation Claude waits for before changing anything in your 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 Fyxer.
Connect Fyxer to Claude in three steps
- 01
Find Fyxer in Claude
Open Claude's settings, go through Customize then Connectors, and look for Fyxer in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first, before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Fyxer in the window Fyxer opens itself. If the link breaks later, use Disconnect and connect again; access can also be withdrawn from the Fyxer side.
- 03
Read the authorization screen
Go through Fyxer's authorization screen before you accept. It belongs to the service, not to Claude, and it sets what the access covers. The access is granted once, for you alone, and you can take it back the same way.
The 8 tools, grouped by what they do
Fyxer gives Claude 8 tools: 5 that read your account, 1 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, the one tool that writes a draft, and two tools no source explains. Names stay exactly as Claude shows them.
- 5 read
- 1 write
- 2 not documented
What Claude reads (5)
5 toolsFive tools that search and open your mail, meetings and contacts without changing them.
search_context
A single query that sweeps your emails, your meetings and your documents at once, so Claude can surface action items, decisions or a thread you half remember without you naming where it lives.
search_meetings
Looks up meetings and call recordings by subject or by who attended, and hands Claude the list of matching sessions to work from.
get_meeting
Opens the complete summary Fyxer keeps for one specific meeting, the one Fyxer already produced, without going back to the recording or the transcript.
get_transcript
Brings back the word-for-word record of a call, with the speaker notes Fyxer attaches, so Claude can work from what was actually said rather than a recap.
resolve_person
Looks up a contact and returns that person's name and email address, so the reply goes to the right inbox instead of a guessed one.
What Claude writes (1)
1 toolOne tool that produces an email draft. No source describes a confirmation for it: the general rule below applies.
draft_email
Approval: see the ruleWrites an email in your own style and shows it inside the chat. From there you choose to open it in Outlook or Gmail, where it lands as a draft you can edit; Fyxer never sends it for you.
Not documented (2)
2 toolsListed on the directory sheet by name only. No official source says whether they read or change anything.
find_recordings
Neither Fyxer's help article nor any Claude page describes this one: the directory publishes its name and nothing else. We make no claim about what it touches or returns, and the general approval rule below is the only reference that applies to it.
get_recording
Like find_recordings, this tool has no description anywhere: it sits on the directory sheet, yet no table from the publisher includes it. Its effect is therefore unknown here, and any confirmation follows the default rule described further down this page.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account in your place. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do for the whole organisation, for instance keep reading open and shut writing, and nobody overrides that from a personal account. Claude also works with your rights and no more: Fyxer says it only reaches data from the accounts you connected yourself.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that answer is published nowhere: it is a real hole in the catalogue.
What is published is the general rule: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organisation before members connect. For this one's current state, check its sheet in the official directory. Note that only Fyxer documents it; no Claude help page covers it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing fires when a new email arrives or a meeting ends.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The partner badge in the directory is not a security audit either, and Anthropic notes on every sheet that it does not pick the tools a publisher exposes or guarantee they behave as described. Only connect what comes from a publisher you trust. To compare with a connector from another publisher, see the Claude affinity connector page.
Need help connecting Fyxer to Claude?
A person reads every message.
