Fyxer

Draft an email adapted to the user's writing style, to match their voice. Returns the generated subject and body as text; nothing is saved to the user's mailbox or sent. Present the returned body as it is; do not rewrite its wording. Use resolve_person first if you only have names — every recipient needs an email address.

Find recordings (captured meeting contents — transcript and/or summary) by title, attendees, summary text, date, or participants. Answers 'which recording?', not 'what was said'. Use search_context for content (decisions, action items, facts, status updates); fall back to it if this returns nothing relevant. 'Call', 'recorded meeting', and 'conversation' are synonyms for a recording. Current date: 2026-11-01. DATE EXTRACTION RULES: 1. When user mentions ANY temporal expression, you MUST calculate and extract from/to dates as ISO 8601 strings 2. Temporal expressions include: today, yesterday, 2 days ago, this week, last week, previous week, this month, last 3 months, past 7 days, recent, etc. 3. Calculate the EXACT start and end dates based on current date above 4. Use T00:00:00Z for start times and T23:59:59Z for end times 5. Relative expressions ('2 days ago', 'last 3 months', 'recent') should be calculated from current date 6. 'recent', 'most recent', 'latest' without specific timeframe = past 30 days Set maxResults to 1 for singular queries ('last', 'latest', 'most recent') and 10 for plural/broad queries.

DEPRECATED: this tool was renamed to get_recording. Calls continue to work and return identical results, but new integrations should use get_recording instead. Get details for a recording by ID: meeting metadata, summary, parsed sections, transcript preview, and action items. A recording is the captured contents of a meeting. Use get_transcript for the full transcript.

Get details for a recording by ID: meeting metadata, summary, parsed sections, transcript preview, and action items. A recording is the captured contents of a meeting. Use get_transcript for the full transcript.

Get the user's Fyxer settings: their shareable scheduling link, timezone, default meeting duration, and working days. Use when the user wants their scheduling/booking link or their availability defaults.

Get the full transcript of a meeting by ID, paginated. If pagination.hasMore, call again with offset = pagination.offset + pagination.returnedSegments. If totalSegments is 0 the meeting was not recorded; tell the user that rather than retrying or reporting an error.

Find the top 10 most likely people (name and email) being referenced in a natural language query. Returns an array of people ordered by relevance/confidence. Use this when the user refers to someone by name only, without providing their email address — for example before draft_email when you only have a name.

Search extracted knowledge from the user's meetings, emails, and documents. Returns specific items that were said, decided, assigned, asked, or reported — NOT full meetings, email threads, or documents. contextTypes accepts: action_items, decisions, facts, queries, status_updates, proposals. Source filter accepts: meetings, emails, documents. fallbackKind (optional): 'recency' = recency browse, not a relevance match; 'empty' = no results; 'semantic_only' = loosened/semantic fallback. Absent means a normal match. GOOD for: 'what did we decide about X', 'action items from last month', 'did anyone mention the Nairobi office', 'what's the status on the redesign'. To find a recording by title, attendee, or date rather than its content, use find_recordings instead. Every recording-source result links back to its recording via callRecordingId — chain into get_recording for the full details, or get_transcript for the transcript.

DEPRECATED: this tool was renamed to find_recordings. Calls continue to work and return identical results, but new integrations should use find_recordings instead. Find recordings (captured meeting contents — transcript and/or summary) by title, attendees, summary text, date, or participants. Answers 'which recording?', not 'what was said'. Use search_context for content (decisions, action items, facts, status updates); fall back to it if this returns nothing relevant. 'Call', 'recorded meeting', and 'conversation' are synonyms for a recording. Current date: 2026-11-01. DATE EXTRACTION RULES: 1. When user mentions ANY temporal expression, you MUST calculate and extract from/to dates as ISO 8601 strings 2. Temporal expressions include: today, yesterday, 2 days ago, this week, last week, previous week, this month, last 3 months, past 7 days, recent, etc. 3. Calculate the EXACT start and end dates based on current date above 4. Use T00:00:00Z for start times and T23:59:59Z for end times 5. Relative expressions ('2 days ago', 'last 3 months', 'recent') should be calculated from current date 6. 'recent', 'most recent', 'latest' without specific timeframe = past 30 days Set maxResults to 1 for singular queries ('last', 'latest', 'most recent') and 10 for plural/broad queries.

Search the user's saved Fyxer memories by semantic and keyword similarity. Returns only currently-valid memories: facts, preferences, and relationships the user asked Fyxer to remember. GOOD for: recalling a previously-saved preference, fact, or relationship, e.g. 'what is my preferred meeting length', 'which accounts am I working', 'what did I say about pricing'. Each result includes the memory's content along with when it was saved and last updated.