Build on the registry your team already uses.

Archive (soft-delete) a contact. It moves to Trash and can be restored later, not permanently erased. In the assistant this returns a confirmation card and the contact is archived only when the user confirms; over the API it is archived immediately.

Create up to 100 contacts atomically. Each entry may carry optional `tags` and `custom_fields` for per-contact enrichment (e.g. prospect_intel shapes), and an optional `owner_id` naming the teammate who will own that contact (omit to own it yourself). Any failure mid-batch rolls back the whole transaction: zero contacts are written. Returns {contacts: [<detail>, ...], created_count: N}.

Find work emails for up to 10 people in one call and add each hit as a new reachable contact, with per-person outcomes and the same provenance as find_email (observed vs inferred origin, source URLs, confidence, verification status). People are resolved one by one and the batch is not atomic: contacts already created stay created if a later lookup stops the batch. Per-person status is one of created, not_found, error, or skipped; when the monthly email finder quota runs out or the provider fails mid-batch, the batch stops and stopped_early names the reason with every remaining person reported as skipped, never dropped. Needs email finding enabled for the workspace.

Correct a contact's email address, with provenance. update_contact deliberately cannot change email (an identity-stable patch); this is the audited path for fixing a wrong address. Requires provenance_url naming where the corrected address was observed; it is recorded in the audit trail beside the previous value. Returns a typed conflict when another active contact already has the address. Resets the bounce flag set against the old address and re-derives suppression for the new one. Stamps the email provenance custom fields (email_source correction, email_status unverified). Returns {contact, previous_email}.

Create a new contact in the tenant's CRM.

The real schema of the CRM records you can read and write: per-entity columns with their type, nullability, and foreign keys, plus this tenant's custom fields (on contact/company/deal). Call it to answer what fields/columns an entity has. Report what it returns, never infer the schema from a tool's arguments. Pass an entity to scope it, or omit for all.

Find a person's work email from their name + company (domain or name) and add them as a new reachable contact, with the email's provenance recorded: whether the address was observed on real web pages (with source URLs) or inferred from a pattern, plus confidence and verification status. Searches the open web first at no cost; a paid search runs only on a web miss and counts toward the workspace's monthly email finder quota. Confirms before the lookup + create. If no email is found, nothing is created; QUOTA_EXHAUSTED means the monthly allowance is used up and FINDER_UNAVAILABLE means the provider failed, so not_found always means a real miss. Needs email finding enabled for the workspace. Returns the resolved email + the created contact, or that none was found.

Email-keyed find-or-create. Looks up the tenant's contacts by lowercased email; returns the existing record if matched, otherwise creates with the supplied fields. `first_name` and `last_name` are required only on the create path. `tags` and `custom_fields` apply only on the create path; the find branch returns the existing record unchanged, and any provided field that differs from the matched record is named in the response's warnings so the drop is never silent. Returns {contact, created: bool}.

Find contacts semantically similar to a seed contact (by contact_id) or to a free-text description (by query). Exactly one must be given. Returns contacts ranked nearest-first as {contact, distance} (cosine distance, 0 = identical). An unindexed seed returns an empty list.

Get full details for a specific contact by id.

Restore a soft-deleted contact from Trash back to active (the inverse of archive_contact). In the assistant this returns a confirmation card and the contact is restored only when the user confirms; over the API it is restored immediately. Use this to undo an archive. Refuses if the contact isn't in the trash.

Search contacts by name, email, or company, or omit query to list them. Results are ordered by sort_by, newest first, so no query with the default sort returns the most recently added contacts. Can filter to the current user's own contacts (mine), one teammate's (owner_id), unassigned contacts with no owner (unowned), a tag, a status, one company (company_id), whether the contact has a dialable phone number (has_phone), or untouched leads. Returns the matched rows plus the total matched count; when total exceeds the page, fetch the rest with page=2, 3, …

Partially update a contact's editable fields.

Archive (soft-delete) a company. It moves to Trash and can be restored later, not permanently erased. Its contacts are unlinked (not deleted). In the assistant this returns a confirmation card and the company is archived only when the user confirms; over the API it is archived immediately.

Create a new company in the tenant's CRM. Mirrors the REST POST /companies endpoint.

Find-or-create on the canonical match key: normalised domain first, then case-insensitive name among active companies. Returns the existing record if either key matches (a name-match backfills a missing domain), otherwise creates with the supplied fields. tags, custom_fields, source and the other extras apply only on the create path: the find branch returns the existing record as-is without mutating it (updating a match is a separate update_company call), and any provided field that differs from the matched record is named in the response's warnings so the drop is never silent. `name` is required only on the create path. Returns {company, created: bool}.

Find companies semantically similar to a seed company (by company_id) or to a free-text description (by query). Exactly one must be given. Returns companies ranked nearest-first as {company, distance} (cosine distance, 0 = identical). An unindexed seed returns an empty list.

Get full details for a company by id, including contacts.

List contacts that belong to a specific company.

Restore a soft-deleted company from Trash back to active (the inverse of archive_company). In the assistant this returns a confirmation card and the company is restored only when the user confirms; over the API it is restored immediately. Contacts that were unlinked at delete time are NOT re-linked. Refuses if the company isn't in the trash.

Search companies by name or domain. Returns {companies, total} with contact counts, owner and location; when total exceeds the page, fetch the rest with page=2, 3, … Can filter to the current user's own companies (mine), one teammate's (owner_id), unassigned companies with no owner (unowned), companies carrying a tag (tag), a city, a region or nation, a country, a research source, a prospect-intel fit_rating or a prospect_stage. Filter here rather than paging and sorting on your side: geography and fit are the two things that used to require reading every company one at a time. For Scotland or England use region, not country: both nations store country=United Kingdom.

Update a company's fields. Pass only the fields to change. Domain input is canonicalised (scheme/path stripped).

Archive (soft-delete) a deal. It moves to Trash and can be restored later, not permanently erased. In the assistant this returns a confirmation card and the deal is archived only when the user confirms; over the API it is archived immediately.

Create a new deal in the pipeline. Requires a contact; company is optional. Value is in cents. Stage defaults to the tenant's first open pipeline stage if omitted.

Find deals semantically similar to a seed deal (by deal_id) or to a free-text description (by query). Exactly one must be given. Returns deals ranked nearest-first as {deal, distance} (cosine distance, 0 = identical). An unindexed seed returns an empty list. Use for 'find deals like our best closed ones' or 'deals about platform migrations'; for structured filtering by stage/owner use search_deals.

Get full details for a specific deal by id.

Current deal pipeline grouped by stage with totals.

Restore a soft-deleted deal from Trash back to active (the inverse of archive_deal). In the assistant this returns a confirmation card and the deal is restored only when the user confirms; over the API it is restored immediately. Use this to undo an archive. Refuses if the deal isn't in the trash.

Search and filter deals. Supports filtering by stage, owner, contact, or company; use mine for the current user's own deals. Optional text query matches deal title. Returns {deals, total}; when total exceeds the page, fetch the rest with page=2, 3, …

Update a deal's fields. Pass only the fields to change. Stage changes are audited with direction (forward/backward).

Archive (soft-delete) a task. It moves to Trash and can be restored later with restore_task, not permanently erased. In the assistant this returns a confirmation card and the task is archived only when the user confirms; over the API it is archived immediately.

Mark a task as completed. Idempotent if already completed.

Create a follow-up task. Optionally attach to a contact, deal, or company. Assignee defaults to the current user.

Get open tasks assigned to the current user, sorted by due date (overdue first, then upcoming, then no-date). Use this whenever the user asks about their own tasks.

List tasks, optionally filtered by entity or assignee. Returns open tasks by default; set include_completed=true for all.

Restore a soft-deleted task from Trash back to active (the inverse of archive_task). Find the task_id with search_trash, which lists archived records. In the assistant this returns a confirmation card and the task is restored only when the user confirms; over the API it is restored immediately. Refuses if the task isn't in the trash.

Edit an existing task: reschedule (due_at; null clears the due date), set status (todo/in_progress/waiting/done), priority, size (s/m/l), reassign, rename, edit the description, or re-link it to a contact, deal, or company. Only the fields provided change; setting status to 'done' completes the task and leaving 'done' reopens it.

Add a note to a contact, deal, or company, or a comment to a task. To @-mention a teammate so they get notified, write @[Their Name](user:<user_id>) in the body. User ids come from list_users.

List notes attached to a contact, deal, company, or task (a task's notes are its comments). Returns newest first.

List notes created across ALL records in the last N days, newest first, optionally filtered to notes whose body contains a given text. Use for 'any notes about pricing this week?' or 'what did I note recently?' when you don't have a specific record in hand. For notes on ONE known record, use list_entity_notes instead.

Semantic search across ALL note bodies: matches by meaning, not substring, so 'pricing pushback' finds a note that says 'thought the quote was steep'. Returns notes ranked nearest-first with their parent record reference and a cosine distance (0 = identical). Use when the user half-remembers a note; for literal text or a time window use recent_notes, and for one known record use list_entity_notes.

Edit an existing note or task-comment: replace its body with new text (pass the whole body, not a diff). The note keeps its author and parent record. Get the note_id from list_entity_notes, recent_notes, or search_notes. Only the note's author or an admin may edit it.

List meetings logged against a contact, company, or deal. Returns newest first.

Log a meeting against a contact, company, or deal: date, duration, attendees, location, and notes. Records a past or scheduled meeting; surfaces on the entity's timeline.

List meetings logged across ALL records in the last N days, newest first, optionally narrowed to one entity kind. Use for 'what meetings happened this week?' when you don't have a specific record in hand. For meetings on ONE known record, use list_meetings instead. Distinct from list_upcoming_events, which reads the user's real connected calendar.

Edit a logged meeting's details: title, when it happened, duration, location, or notes. Pass only the fields to change. Get the meeting_id from list_meetings or recent_meetings. This edits a logged meeting record; for a calendar invite use update_calendar_event instead.

List captured calls (uploaded recordings with an AI transcript and summary), newest first. Calls are logged against a contact, company, or deal, or are the team's internal calls (standups, deal reviews) via entity_type 'internal' with no entity_id. Returns each call's title, date, transcript/summary status, AI summary, sentiment, action items, and suggested next step. Use to recall what was discussed on recent calls with a record or in team meetings.

Generate a {subject, body} email draft from a brief, using the tenant's configured LLM. Read-only: no DB write. The caller passes the returned draft to send_one_off_email (or discards it). Optional reply_to_outreach_id enriches the prompt with the inbound thread for reply drafting.

Aggregate outreach stats for a date range or campaign by name. Returns total_sent, total_replied, reply_rate, open_rate, bounce_rate, by_channel.

Get the most recent outreach records for a contact.

Most recent outreach records, optionally filtered to one contact. Useful for context before drafting a follow-up.

Record an outreach event against a contact.

Stage a single-recipient email send through the human-approval queue (M33d). Creates a pending SendApprovalRequest backed by an implicit one-off campaign; a human must approve in the Limena UI before the email leaves. Idempotent within 5 minutes per tenant+contact. When reply_to_outreach_id is supplied (M33f), the send is threaded as a reply to that inbound message: In-Reply-To and References headers are attached to the outgoing email and, for Gmail, the message lands in the same conversation.

Bulk-record outreach status updates from an external mailmerge tool. Unmatched emails create new contacts; the response lists them.

Add individual contacts to a campaign as manual-source recipients. Up to 500 contacts per call. Idempotent: contacts already in the campaign via this source are silently skipped. Returns suppression breakdown (unsubscribed, email_invalid).

Add all contacts from a prospect list to a campaign. Auto-promotes eligible list items to contacts. Returns suppression breakdown and promotion count.

Add contacts matching a saved segment to a campaign. Snapshot at add-time. Re-add the segment to pick up new matches. Returns suppression breakdown.

Cancel a campaign send that is sending, paused, or scheduled. Already-sent messages are not retracted, so cancelling a send that has started cannot be undone. Cancelling a scheduled send that has not fired yet only removes the schedule: an AI campaign returns to its review queue with its drafts intact and can be scheduled again.

Check the status of a send approval request. Returns pending, approved, or rejected with decision details, plus recipients_blocked_unverified (addresses that were pattern-derived and never checked, already excluded from the send) and recipients_unconfirmed (addresses that WILL be sent to but carry no record of where they came from). Read both before approving a send.

Create a new campaign. Idempotent: returns the existing campaign if one with the same name already exists.

Get campaign detail including member count, outreach count, send status, and last sent date.

List contacts that are members of a campaign.

Pause a campaign that is currently sending. Already-queued messages will self-skip. Resume must be done by a human via the UI.

Remove a contact from a campaign across all sources. Idempotent: returns removed=false if the contact was not a member.

Request approval to send a campaign. Creates a pending approval that a human must approve or reject in the Limena UI before any emails are sent. Returns the approval ID for polling via check_send_approval. Idempotent: a second call while one is pending returns the existing approval.

Update campaign metadata. Only send the fields you want to change. Supports: name, description, compose_mode (template, ai_generated, or ai_templated), tracking_enabled, system_prompt_override.

List file attachments on a contact, deal, company, task, or note. Returns newest first. Read-only: uploads + deletes go through the REST API.

Hybrid keyword + semantic search across the CRM. Exact name / email / title matches rank first; contacts and companies also surface semantically related records a keyword miss would skip. Returns up to per_type results in each bucket: contacts, companies, campaigns, deals, outreach.

ONE semantic search across the whole workspace (contacts, companies, deals, notes, calls, email threads, meetings, tasks, form submissions and document attachments), ranked nearest-first by meaning with a relevance cutoff. Use FIRST for open 'what do we know about X' questions instead of fanning out across per-type search tools; each hit is a compact {entity_type, id, label, snippet, date, distance} line; follow up with the type's detail read for anything relevant. For structured filtering (stage, status, owner lists) use the per-type search tools; for exact-name lookup use search_crm.

Search the Trash (soft-deleted, archived contacts, companies, deals and tasks) by name, title or subject. The regular search tools never return archived records; this one returns ONLY them, each as a {entity_type, id, label, archived_at} line. Use it to find a record to bring back that was archived in another conversation, then call restore_contact / restore_company / restore_deal / restore_task with the id. Omit the query to list everything currently in the trash.

Compare reply rates or open rates across named campaigns.

Total record count for a tenant-scoped entity, with the same typed filters as the search tools so 'how many companies are unassigned' is one call.

List all campaigns for the tenant with member and outreach counts. Use to discover campaign names before filtering by them.

Breakdown of outreach volume and reply rates by channel.

Aggregate outreach stats for a date range / campaign.

Natural language analytics question. Delegates to the AnalyticsAgent; consumes LLM tokens; rate-limited 10/hour.

Most recent outreach and deal stage changes.

List contacts ranked by engagement metric. Each result carries its contact_id, usable directly in follow-up calls (add to campaign, update, get) without re-searching by name.

List the tenant's active team members. Useful for discovering user IDs when assigning tasks or deal ownership. Deactivated accounts are never listed, because they cannot be assigned work.

Reassign a set of companies (by id, 1 to 100) to a single owner in one step. In the assistant the whole set is shown as one confirmation card before anything changes; over the API it applies immediately, so pass dry_run=true first to see the exact set. Omit owner_id to assign them to yourself; pass a teammate's owner_id (resolve it with list_users) to assign to them; set unassign=true to clear the owner. Resolve the set first with search_companies (e.g. unowned=true) so you act on the exact companies. Returns {matched, affected, skipped}.

Reassign a set of contacts (by id, 1 to 100) to a single owner in one step. In the assistant the whole set is shown as one confirmation card before anything changes; over the API it applies immediately, so pass dry_run=true first to see the exact set. Omit owner_id to assign them to yourself; pass a teammate's owner_id (resolve it with list_users) to assign to them; set unassign=true to clear the owner. Resolve the set first with search_contacts (e.g. unowned=true) so you act on the exact contacts. Returns {matched, affected, skipped}.

Reassign a set of deals (by id, 1 to 100) to a single owner in one step. In the assistant the whole set is shown as one confirmation card before anything changes; over the API it applies immediately, so pass dry_run=true first to see the exact set. Omit owner_id to assign them to yourself; pass a teammate's owner_id (resolve it with list_users) to assign to them. A deal always has an owner, so it cannot be unassigned. Resolve the set first with search_deals so you act on the exact deals. Returns {matched, affected, skipped}.

Set the lifecycle status on a set of contacts (by id, 1 to 100) in one step. In the assistant the whole set is shown as one confirmation card before anything changes; over the API it applies immediately, so pass dry_run=true first to see the exact set. The status must be one of the tenant's configured statuses (setting 'unsubscribed' also suppresses future outreach). Resolve the set first with search_contacts so you act on the exact contacts. Returns {matched, affected, skipped}.

Add or remove tags on a set of companies (by id, 1 to 100) in one step. In the assistant the whole set is shown as one confirmation card before anything changes; over the API it applies immediately, so pass dry_run=true first to see the exact set. mode='add' adds every tag to every company (idempotent); mode='remove' removes them. Resolve the set first with search_companies so you act on the exact companies. Returns {matched, affected, skipped}.

Add or remove tags on a set of contacts (by id, 1 to 100) in one step. In the assistant the whole set is shown as one confirmation card before anything changes; over the API it applies immediately, so pass dry_run=true first to see the exact set. mode='add' adds every tag to every contact (idempotent); mode='remove' removes them. Resolve the set first with search_contacts so you act on the exact contacts. Returns {matched, affected, skipped}.

Get one CSV import job by id with its status, imported/duplicate/error counts, failure reason, and whether an error report is available. Use to explain how an import went.

Get one CRM migration job by id with its overall status, per-file breakdown (each file's entity type, status, row + error counts), the unresolved-foreign-key count, and any failure reason. Use to explain how a migration went, file by file.

List the tenant's single-file CSV import jobs, newest first, each with its status, row counts, and any failure reason. Use to answer 'did my import finish' or to find a job to inspect.

List the tenant's multi-file CRM migration jobs (e.g. a HubSpot export), newest first, each with its vendor, status, file count, and error count. Use to answer 'did my migration finish'.

Stage a set of researched prospects as a new prospect list, so the existing list pipeline (dedupe, cross-reference against the user's contacts, disposition) takes over. Use this to save the results of a web research request. Columns are kept as given. In the assistant the user confirms before the list is created, so say it was proposed and is awaiting confirmation; over the API it is created immediately.

Get one prospect list by id with its per-disposition cleaning breakdown (safe-to-email, duplicate, previously-contacted, invalid email) and the known-contact tally. Use to report how a list cleaned, or to check it before promoting its safe rows to contacts.

List the tenant's prospect lists (uploaded or AI-researched), newest first, with each list's cleaning progress and safe-to-email count. Use to answer 'what lists do I have' or to find a list before reading or promoting it.

Promote a prospect list's safe-to-email rows to CRM contacts (creating companies as needed). Already-known people are linked, not duplicated. Reports how many were created, already existed, or were skipped. In the assistant the user confirms before any contact is created; over the API it runs immediately, so check the list with get_prospect_list first.

Save a named, reusable contact segment from a structured SegmentQuery filter. Deterministic: the query is compile-checked against the field registry and stored as given, with nothing generated. Fails cleanly if the name is already taken. Use list_segments to see what exists first.

Permanently delete a saved segment (the named filter only. No contacts are touched, and campaigns already built from it keep their recipients). There is no trash for segments, so this cannot be undone. Get the segment_id from list_segments.

List the tenant's saved segments (named, reusable filters over contacts, e.g. 'UK prospects, no email in 30 days'), newest first. Use to find a segment to report on or to target with a campaign.

Rename a saved segment and/or replace its filter query (the query replaces wholesale, not a merge: send the complete new SegmentQuery). At least one of name or query is required. Get the segment_id from list_segments.

List the workspace's whole tag vocabulary, alphabetically, with the number of records carrying each tag and the slug it is matched on. Read this BEFORE writing tags on a contact or company: a tag name is matched by its slug (lowercased, every run of non-alphanumeric characters becomes a hyphen), so 'M&A' and 'M and A' are different tags, and writing a name that slugs differently from an existing tag silently creates a near-duplicate rather than reusing it.

Find existing tags matching a piece of text, ranked exact-slug then prefix then substring, most-used first. Use it to check whether a tag you are about to write already exists under a different spelling before you create a second one.

Save a reusable email/campaign template from an explicit subject and body. Deterministic: the text is stored as given and nothing is generated. Fails cleanly if the name is already taken (use list_email_templates to check). Merge variables are {{double_braced}} and the contact ones are bare, not namespaced: {{first_name}}, {{last_name}}, {{email}}, {{phone}}, {{job_title}}, {{linkedin_url}}, plus {{company.name}} (the only dotted one) and the tenant's own {{custom:<key>}} fields. Anything else, such as {{contact.first_name}} or {{company_name}} or {{company.domain}}, is not a variable and sends as an empty string, so the result lists any it does not recognise under `warnings`. Do not add a {{signature}} or a written sign-off: the sender's signature is appended automatically at send time.

Get one email template by id with its full subject, body, and merge variables. Use to read or reuse a template's content when drafting an email.

List the tenant's saved email/campaign templates, most-recently-updated first, optionally filtered by folder. Returns each template's name, subject, merge variables, and folder. Use to find a template to reuse or reference.

Edit a saved email template: rename it, replace its subject or body (each replaces wholesale, not a diff), or refile it. At least one change is required. Get the template_id from list_email_templates. Merge variables are {{double_braced}} and the contact ones are bare, not namespaced: {{first_name}}, {{last_name}}, {{email}}, {{phone}}, {{job_title}}, {{linkedin_url}}, plus {{company.name}} (the only dotted one) and the tenant's own {{custom:<key>}} fields. Anything else, such as {{contact.first_name}} or {{company_name}} or {{company.domain}}, is not a variable and sends as an empty string, so the result lists any it does not recognise under `warnings`. Do not add a {{signature}} or a written sign-off: the sender's signature is appended automatically at send time.