Levitate

Reports whether the user's connected mailbox can reply inside an existing conversation, and what a reply can carry there. Call this before promising a reply with an attachment or exact formatting. Supported=false means email_provider_reply will refuse for this mailbox; say so rather than falling back to email_provider_send, which would reach the recipient as a detached new message.

email_provider_reply_capability

Mark an action item as completed. Once completed, the action item's completion date is set to the current time. To reopen a completed action item, call action_items_update with isCompleted=false. Examples: - "Mark my follow-up call task as done" → provide the actionItemId - "Complete the proposal task" → provide the actionItemId Use action_items_search to find the action item ID first.

action_items_complete

Create a new action item (task, to-do, reminder, or follow-up) that can be assigned to users and associated with contacts. IMPORTANT: The assigneeId parameter and the response fields AssigneeId/CreatorId contain user IDs, not names. - To assign to yourself, omit assigneeId (defaults to current user) or call users_get_self first to get your user ID. - To assign to someone else, call users_search to find their user ID first. Examples: - "Create a task to call John next Friday" → provide description, contactId (from contacts_search), and dueDate - "Remind me to send a proposal by end of week" → provide description and dueDate - "Add a follow-up task for the team lead" → provide description and assigneeId Action items must have future due dates. Past dates will be rejected.

action_items_create

Create a new custom survey shell with branding, an optional date window, and per-field contact-info requirements. This creates the survey but does not add any questions — use surveys_question_add for that, in the order they should appear. Read the custom_survey_creation resource (levitate://custom-survey-creation) before calling — it explains the two-phase create-then-add-questions flow, the three-state contact-info model, and how to wire question-visibility branching using IDs returned from prior calls. Returns the newly created survey's ID. Hold on to it — every surveys_question_add call needs it. Requires the account's Surveys feature. If it is off, this fails with "Surveys aren't enabled on this account" — relay that to the user rather than retrying or working around it, and do not start the question-design conversation until it is on.

surveys_custom_create

Create a draft email in the user's connected email provider. The draft lands in their Drafts folder — it is NOT sent. The user must review and send it themselves from their email client. Returns the provider draft id and a web link (when available). Note — drafts created here live only in the user's mailbox and are not logged or tracked in Levitate. For outreach to contacts that should appear on their Levitate timeline (with open/reply tracking and compliance handling), use email_campaigns_create instead; reserve this tool for when the user explicitly wants a draft in their own email client. Supported on Gmail, Microsoft 365 (Outlook), and on-prem Exchange (EWS); IMAP and SMTP-only providers return an error. WebLink: Outlook links directly to the draft. Gmail links to the Drafts folder of the user's default Google account in their browser — Gmail's API has no per-draft URL, and the link can land on the wrong account if the user has multiple Google accounts signed in. Exchange returns no web link. Provide at least one of: a recipient (to/cc/bcc), a subject, or a body. Optional inline attachments (base64) may be supplied; combined size is capped at the maximum message size the user's email provider allows. They are passed through to the provider with this draft only and are NOT persisted to Levitate.

email_provider_create_draft

Create a new contact. Supply either both a first and last name, or an email address (at minimum one of those). The company is inferred from the email domain and visibility defaults to your account's default — do not pass them. To tag the contact, pass `tags` (maximum 10). Ground tag names with `tags_search` first so you reuse the account's existing tags (e.g. "VIP") instead of creating near-duplicates. Unknown tags are created automatically. If a contact with the given email already exists, this returns an error instead of creating a duplicate — fall back to `contacts_search` to find the existing contact and `contacts_add_tags` to tag it.

contacts_create

Create a DRAFT blog post. The draft is never published by this tool: it stays unscheduled until blogs_schedule is called, and the account's compliance review still applies at that point. Read the levitate://blog-post-creation guide before using this tool. Content — pass the body as HTML (`<h2>`/`<h3>` subheadings, `<p>` paragraphs, `<ul>`/`<ol>` lists). Do NOT include the title as an `<h1>` in the body; the title is a separate field and the site renders it. ALWAYS show the user the title and the body and get their confirmation before creating the draft. Images — optionally attach one main/hero image: upload it with files_create_upload first, then pass its fileId as mainImage. Images inside the body must be added in Levitate.

blogs_create_draft

Create a DRAFT social media post. The draft is never published by this tool: it stays unscheduled until social_posts_schedule is called, and account rules (compliance review) still apply at that point. Read the levitate://social-post-creation guide before using this tool. Targets — provide one or more pages from social_connections_list, each {provider, pageId}. Every target must be a Connected account the current user owns; an unknown or disconnected page is rejected. Content — plain text up to 2,200 characters. Do NOT include the user's social signature or any required disclosure; those are appended automatically at publish time. ALWAYS show the user the content and the target pages and get their confirmation before creating the draft. A Facebook Page mention is written inline as {{@Page Name|PAGE_ID}}; only Facebook tags the Page, Instagram and LinkedIn publish the name. Images — optionally attach up to 10 images (no video; add video in Levitate). Upload each image with files_create_upload first, then pass its fileId here. Instagram REQUIRES at least one image: an Instagram target with no image is created as a draft but is rejected at schedule time, so attach an image here (or in Levitate) before scheduling it.

social_posts_create_draft

Create a new text note associated with a specific contact. Use this tool to: - Add notes, observations, or comments about a contact - Record meeting notes, phone call summaries, or conversation details - Log follow-up reminders or next steps - Document interactions, touchpoints, or relationship history The note is automatically linked to the specified contact and appears in their timeline.

notes_create

Create an email campaign AND schedule it to start sending after `startDate`, in one step. There is no unscheduled "draft" state: a campaign created here is committed to send (subject to the lead time below, and to compliance approval when the account requires it). Use email_campaigns_cancel to stop it before it starts. ALWAYS confirm the subject, body, audience, AND the exact start date with the user before calling this tool — once the start date arrives it sends real email to real contacts. The required lead time guarantees the creator gets Levitate's day-before reminder and a window to cancel, but that is a safety net, not a substitute for confirming first. This is the DEFAULT way to email contacts through Levitate: sends are logged on each contact's timeline, tracked (opens, replies, clicks), and honor the account's compliance, approval, and unsubscribe rules. Do NOT use email_provider_send / email_provider_create_draft for contact outreach — those bypass Levitate entirely and are reserved for when the user explicitly asks to send directly from their own mailbox. Read the levitate://email-campaign-creation guide before using this tool. Start date (required, ISO 8601, e.g. '2026-06-10T14:00:00Z'): - Immediate sends are not available; the date must be in the future. - Self-sends require ~25 hours of lead time (so the creator receives the day-before reminder and can cancel). - On-behalf sends require the account's send-on-behalf wait time (default 2 days). - A too-early date is rejected with the earliest allowed value. To preview the projected send window for a large audience before committing, you can create it, then call email_campaigns_estimate / email_campaigns_get, and email_campaigns_cancel if the user changes their mind (the lead time leaves ample room). Audience — provide exactly one of: - recipients: an explicit list of contacts (max 500), each {contactId, optional subject, optional htmlBody}. Use contacts_search to find IDs. - filter parameters (tags / companyName / location / lastCommunicatedDateRange): resolved the same way as contacts_search. Use contacts_search with the same parameters first to preview who will be targeted. Content — provide htmlBody, or templateId to start from an existing template (htmlBody then overrides the template body if both are given). Attachments — optionally attach files (PDFs, images, etc.). Upload each with files_create_upload first, then pass its fileId in `attachments`; the bytes never pass through this tool. Combined size must stay within the user's email provider per-message limit. To make an image appear inline in the body, embed it in the HTML instead — attachments are sent as downloadable files. Per-contact customization — the campaign-level subject/htmlBody are the default for everyone. To tailor a specific recipient (a bespoke sentence for a VIP, a different opening), set subject and/or htmlBody on that entry in `recipients`; it overrides the default for that contact only. This is for variation that ISN'T expressible as a merge placeholder — for "insert each person's first name", use a {{placeholder}} in the default body instead of customizing every recipient. Per-contact customization is only available with the explicit `recipients` audience, not the filter audience. Personalization — you may insert merge placeholders in the subject and body (campaign-level OR per-contact) using {{placeholder}} syntax, written as plain text (e.g. "Hi {{first name}},"); each is filled in per recipient at send time. Call email_placeholders_list for the supported placeholders — any other or malformed {{...}} is rejected so a broken token can't reach a contact. Do not hand-write placeholder HTML. Compliance: on accounts with compliance review enabled, the campaign is automatically routed through approval — it is created on hold and will not send until a reviewer approves it in Levitate. The response Campaign.Status will be WaitingForApproval in that case, and the schedule takes effect once approved. You cannot skip this from the agent. Sending on behalf of another user requires the account's send-on-behalf feature and admin permission, and is subject to compliance approval and a longer scheduling lead time (account's wait time, default 2 days).

email_campaigns_create

Permanently delete an action item. Prefer action_items_complete when the work was done; delete only when the item was created by mistake or is no longer relevant. Keep-in-touch reminders cannot be deleted. Use action_items_search to find the action item ID first.

action_items_delete

Saves a threaded reply as a DRAFT in the user's mailbox without sending it, so they can read it over and send it themselves. Prefer this over email_provider_reply whenever the user has not clearly asked for the reply to go out immediately. Pass a providerMessageId from email_provider_search or email_provider_get_message. Recipients are derived from that message exactly as with email_provider_reply: replying to a message the user SENT addresses the people it was sent to, as following up on it in a mail client would. Not every mailbox can do this: IMAP and SMTP connections have no drafts at all, and Microsoft 365 needs the user to have granted mailbox write access. Call email_provider_reply_capability first when unsure; a refusal here explains which of the two applies.

email_provider_draft_reply

Dry-run a campaign send to preview the audience size and the projected send window before scheduling. The projection accounts for the account's daily send limits (large campaigns are spread across days), business hours, and holidays. ALWAYS call this before email_campaigns_schedule: the response includes `minimumAllowedStartDate`, the earliest start date the schedule tool will accept for this campaign, so you can propose a valid date the first time. Nothing is sent or scheduled by this tool.

email_campaigns_estimate

Get a single action item by ID, including its text, due date, priority, assignee, completion state, and referenced contacts. Use action_items_search to find the ID first when you only know what the task is about.

action_items_get

Fetch full details for a single meeting by provider meeting ID. Returns description, attendees with RSVP status and resolved Levitate contact IDs (when matchable), conferencing URL, and deep links. Use this after calendar_provider_search when you need attendee details or description content beyond the lightweight search result. When the meeting is not found or cannot be fetched, the response has Found=false and Meeting=null.

calendar_provider_get_meeting

Fetch full email message details (including body content) from the user's connected email provider. Primary usage: Pass providerMessageIds from email_provider_search results for direct message retrieval. Fallback usage: Pass contactId with a date range to search for messages (slower, less precise). This retrieves content directly from the provider (Gmail, Outlook, Exchange), NOT from Levitate bulk emails or campaigns.

email_provider_get_message

Return metadata for an uploaded file by id, including a short-lived signed download URL for ready files. Does not return the file bytes.

files_get

Return a user's profile by their ID. Use this to resolve user IDs (e.g. AssigneeId, CreatorId from action items) into display names.

users_get

Get a single blog post by ID, including its status, schedule, slug, compliance state, and full HTML body. Use blogs_search to find blog IDs.

blogs_get

Return a company's activity timeline — notes, meetings, sent emails, phone calls, text messages, deals, and follow-ups — most recent first (up to 100 events). Use after `companies_search` to understand the history of interactions with a company. This is the company-level counterpart to `contacts_get_timeline`: it aggregates activity across the company (including its associated contacts), whereas the contact timeline is scoped to a single person. Each event includes its type, timestamp, a human-readable summary, and type-specific details (e.g. email subject and recipients, an action item's due/completion dates).

companies_get_timeline

Return a contact's activity timeline — meetings, sent emails, notes, phone calls, text messages, action items, survey responses, and more — most recent first (up to 100 events). Use after `contacts_search` or `contacts_get_profile` to understand the history of interactions with a contact. Each event includes its type, timestamp, a human-readable summary, and type-specific details (e.g. email subject and recipients, an action item's due/completion dates).

contacts_get_timeline

Return the full profile for a known contact — identity, key dates, tags, custom properties, and communication metadata.

contacts_get_profile

Get a single social media post by ID, including its status, schedule, target pages with per-platform publish state, the post body, and engagement stats. Use social_posts_search to find post IDs.

social_posts_get

Get a single email campaign by ID, including its status, schedule, audience size, engagement stats, the campaign-level HTML body, and which contacts have per-contact overrides. Use email_campaigns_search to find campaign IDs.

email_campaigns_get

Get a single email template by ID, including its full HTML content. Use email_templates_search to find template IDs.

email_templates_get

Return the current authenticated user's profile (ID, name, email, role). Call this FIRST when the user refers to themselves with "my", "me", "I", "mine". Use the returned ID as `assignedTo` in `action_items_search`.

users_get_self

List all opportunity boards and their stages. Call this first to discover board IDs and stage names before searching opportunities. Returns all boards with their stages, including deal size rollup data (total and average) per stage.

opportunities_boards_list

List the current user's connected social media accounts/pages (Facebook, Instagram, LinkedIn). Call this BEFORE social_posts_create_draft: each entry's `pageId` is what you pass as a target's pageId. Only accounts with state `Connected` can publish. An account that is `Disconnected`, `NoTarget`, or whose token has expired must be reconnected by the user in Levitate first — surface that to the user rather than trying to post to it.

social_connections_list

List every folder in the user's Outlook mailbox that email_provider_move_message can move mail into, nested folders included, each with its id and full path (e.g. "Inbox/Clients"). Deleted Items and Outbox are left out because they cannot be move targets. MICROSOFT 365 / OUTLOOK ONLY; other providers return an error. Needs no extra permission beyond the user's existing email connection. Call this before moving rather than guessing a folder name, and pass the path or id it returns.

email_provider_list_folders

List the categories defined in the user's Outlook mailbox — the valid names to pass to email_provider_set_categories, and the ones their existing Outlook rules can match on. MICROSOFT 365 / OUTLOOK ONLY; other providers return an error. Reading the category list needs its own mailbox permission, granted by the same one-time reconnect email_provider_set_categories describes — if the user has not granted it, the error says so and names the link. Treat that as a permission problem to report, NOT as "this mailbox has no categories". Call this before setting categories rather than guessing a name. An empty list from a successful call means the user has genuinely defined no categories yet.

email_provider_list_categories

List the merge placeholders you can use in an email subject or body (including per-contact overrides). Each is replaced per recipient at send time. Write them as plain text (e.g. "Hi {{first name}},") — do not hand-author placeholder HTML. Any {{...}} not in this list, or malformed, is rejected when you create a campaign, so check here rather than guessing.

email_placeholders_list

List a contact's expected documents with their status: `Open` (still owed), `Satisfied` (a received file matched it, or a person confirmed it), `Flagged` (a received file probably matches; needs review — see `matchedSharedFileId` and shared_files_list), or `Waived` (no longer expected). Optionally narrow to one `period`. Counts by status come back alongside the items, so this is also the per-contact progress check. Archived items are excluded unless `includeArchived` is true.

document_checklist_list

List the files exchanged with a contact through Levitate: documents the contact uploaded via a file request, survey or text (direction `Received`) and files sent to them (`Sent`). Each entry carries the file name and size, how it arrived (`origin`), and — when the account has automatic file classification enabled — a `classification` for inbound files: status (`Classified`, `Skipped`, `Failed`), documentType, documentFamily, issuer, period, a one-line description, a suggested file name and a confidence. Classification is always produced from redacted text, so it carries no identifiers or figures from the document (names can appear). Use `direction` to see only what the contact sent. Pagination: up to 50 files per page, newest first. Pass the response's `nextCursor` back as `cursor` to get the next page; the cursor is opaque, not an offset. Use contacts_search to find the contact id.

shared_files_list

Search for donation campaigns by name. Use this tool first when a user asks about donations for a specific campaign by name — call this to resolve the campaign name to an ID, then pass that ID to donations_search. Returns campaigns whose names match the query (partial, case-insensitive). Omit the query to list all campaigns. Pagination: returns up to 10 campaigns per page. To retrieve subsequent pages, pass the response's `nextCursor` back as the `cursor` parameter on the next call. The cursor is opaque — do not construct, parse, or substitute a numeric offset. When `hasMore` is false there are no further pages.

donations_campaign_search

Search for insurance carriers by name. Use this tool first when a user asks about policies for a specific carrier by name — call this to resolve the carrier name to an ID, then pass that ID to policies_search. Returns carriers whose names match the query (partial, case-insensitive). Omit the query to list all carriers. Pagination: returns up to 10 carriers per page. To retrieve subsequent pages, pass the response's `nextCursor` back as the `cursor` parameter on the next call. The cursor is opaque — do not construct, parse, or substitute a numeric offset. When `hasMore` is false there are no further pages.

policies_carriers_search

Search for insurance lines of business by name. Use this tool first when a user asks about policies for a specific line of business by name — call this to resolve the line of business name to an ID, then pass that ID to policies_search. Returns lines of business whose names match the query (partial, case-insensitive). Omit the query to list all lines of business. Pagination: returns up to 10 lines of business per page. To retrieve subsequent pages, pass the response's `nextCursor` back as the `cursor` parameter on the next call. The cursor is opaque — do not construct, parse, or substitute a numeric offset. When `hasMore` is false there are no further pages.

policies_lines_of_business_search

Move a message in the user's mailbox into another existing folder — how a triage classification gets mail that has already arrived filed. Outlook rules only run on delivery, so setting a category on mail already in the mailbox does not move it; this does. MICROSOFT 365 / OUTLOOK ONLY. Gmail, on-prem Exchange, and IMAP/SMTP mailboxes return an error. Requires the same one-time reconnect for mailbox write permission as email_provider_create_draft — if the user has not granted it, the error says so and names the link. Pass providerMessageId from email_provider_search or email_provider_get_message, and destinationFolder as a folder id or full path from email_provider_list_folders (e.g. "Inbox/Clients"). Prefer the id, especially when filing many messages: it resolves directly, while a path or name re-reads the whole folder list on every call. A bare folder name works only when no other folder shares it. The folder must already exist; this never creates one, and Deleted Items and Outbox cannot be targeted. The moved message gets a NEW providerMessageId, returned here — use it for any later call on that message. A NotFound error can mean the message was already moved, including by an earlier attempt of this same call.

email_provider_move_message

Replies to a message in the user's connected mailbox, INSIDE the conversation it belongs to. Use this, not email_provider_send, whenever answering a message the user received. email_provider_send starts a brand new conversation, so a reply sent that way reaches the recipient detached from the thread they started. Pass a providerMessageId from email_provider_search or email_provider_get_message. Recipients are derived from that message rather than supplied: replyAll=false (the default) answers the sender alone, and replyAll=true also copies everyone on the original's To and Cc, minus the user themselves. Following up on a message the user SENT addresses the people it was sent to rather than the user, so the default is the right setting there too. Mailbox differences, which email_provider_reply_capability reports up front: - Microsoft 365 / Outlook quotes the original itself and cannot attach files to a reply. - Gmail, Exchange and IMAP send the body as composed and can attach files. The user is asked to confirm before anything is sent, and the prompt names the resolved recipients, because on a reply they come from the message rather than from this call.

email_provider_reply

Schedule a draft blog post to publish at the given future date, or reschedule one that has not published yet. ALWAYS confirm the exact date with the user before calling this tool — once the date arrives the post is published publicly on the account's blog. Leave `confirm` unset and the user is prompted to approve the post and date where the client supports it; re-issue the call unchanged with their answer. Pass confirm=true only when they have already agreed to this exact post and date. A response noting the user declined leaves any existing schedule untouched — do not retry it. Constraints: - The date must be at least ~15 minutes in the future, leaving a window to review and cancel. - Immediate publishing is not available through this tool. - On accounts with compliance review enabled, the post is routed through approval instead of being scheduled directly: it lands in `Pending` status and only publishes once it is approved in Levitate. The approval goes to YOU (the caller) unless the account has a compliance reviewer address configured, in which case the review request goes there. You cannot choose the reviewer from here. - A Rejected, Cancelled, or Failed post cannot be revived here — handle those in Levitate. Use blogs_cancel to stop a scheduled or pending post before it publishes.

blogs_schedule

Schedule a draft social post to publish at the given future date, or reschedule one that has not published yet. ALWAYS confirm the exact date and the target pages with the user before calling this tool — once the date arrives the post is published publicly to the connected accounts. Constraints: - The start date must be at least ~15 minutes in the future, leaving a window to review and cancel. - Immediate publishing is not available through this tool. - On accounts with compliance review enabled, the post is routed through approval instead of being scheduled directly: it lands in `Pending` status and only publishes once a reviewer approves it in Levitate. Use social_posts_cancel to stop a scheduled or pending post before it publishes.

social_posts_schedule