New Coworker

Get one contact's full profile: name, email, tags, owner, birthday, pinned notes, and the AI's rolling relationship summary.

get_contact

The AiFlow definition format as JSON Schema, plus the step-type and trigger-channel vocabulary. Read this before authoring or editing a flow definition for create_flow / update_flow.

get_flow_schema

List the business's AiFlows (automations): name, enabled state, trigger channel, and last-run time. Use get_flow for a flow's full definition.

list_flows

List every New Coworker business this account can access, with the caller's role on each (owner, manager, or staff). Call this first when other tools report the account has multiple businesses.

list_businesses

List the business's agents — reusable document-processing task templates (instructions run against uploaded files, manually or from run_agent flow steps).

list_agents

The business's leads in motion: contacts with active AiFlow workflow runs (with each run's flow and status) plus lead-state tagged contacts — the same data behind the dashboard Task Center.

list_tasks

Recent activity events for the business, newest first. Event types: sms.inbound, sms.outbound, call.completed, email.inbound. Payloads match the business's outbound webhook format.

list_recent_events

List the business's recent phone calls (AI-handled and human-forwarded), newest first, with status, AI summary, and sentiment when available. Pass a row's fetch_id to the fetch tool to read that call's full transcript.

list_call_transcripts

List the business's employee roster: names, numbers, whether each is active, their working hours, and how each one receives leads (rotation, named group offers, whole-team offers).

list_employees

Read the full record behind an id returned by search: a customer's profile and notes, a whole text conversation, or a call's summary and transcript.

fetch

Read the SMS/RCS conversation with one contact, oldest to newest — inbound texts, the AI coworker's replies, and workflow/manual sends.

get_sms_thread

Run one of the business's ENABLED automations right now (a manual run), the same as pressing Run now in the dashboard. Use this to hand work to a flow directly, e.g. give a new lead's details to the owner's lead-intake automation. `input` is passed to the run as its triggering text, so include everything the flow needs to extract. Unlike trigger_flow (which only reaches webhook-triggered flows), this starts a flow by name or id whatever its trigger, except voice flows, which only run on a live call.

run_flow

Search the business's contacts (CRM) by name or phone substring. Returns basic profile info per contact; use get_contact for the full profile including notes and AI memory.

search_contacts

Find a customer and their text conversation by name or phone number. Returns ids to pass to fetch for the full record. Searches every business this account can access unless business_id is given.

search

Send a WhatsApp message to a customer from the business's connected WhatsApp Business number. Inside the recipient's 24-hour conversation window the text goes out as written; outside it, an approved template carries the message (Meta bills the business per template message). Fails with guidance when WhatsApp isn't connected. If the message mentions a clock time, always include the timezone (e.g. "1:00 PM Eastern", never a bare "1:00 PM"), and when the recipient is known to be in a different timezone, give the time in THEIR timezone too.

send_whatsapp

Send a text message to a customer from the business's phone number. Counts against the business's monthly SMS quota exactly like a dashboard send; the message appears in the owner's Text history. If the message mentions a clock time, always include the timezone (e.g. "1:00 PM Eastern", never a bare "1:00 PM"), and when the recipient is known to be in a different timezone, give the time in THEIR timezone too.

send_sms

Send an event to the business's webhook-triggered AiFlows: every enabled webhook flow whose conditions match the payload gets a queued run (e.g. forward a new lead into the flow engine). Idempotent per event_id.

trigger_flow

Turn one of the business's AiFlow automations on or off. Enabling makes the flow live immediately, so it can start messaging customers the next time its trigger fires; disabling stops new runs without deleting the flow, its steps, or its history.

set_flow_enabled

Update an existing contact: name, email, pinned notes, classification, lead-state tags (pipeline stages are tags), owning team member, or birthday. Tag and owner changes fire the same automations as dashboard edits.

update_contact

Update an agent's name, instructions, output format, or enabled state.

update_agent

Change an existing roster member: their name, number, email, working hours, whether they are active, and how they receive leads. Deactivating someone or turning off lead rotation immediately redirects live leads to other people, so confirm with the owner first.

update_employee

Turn the business's notification/alert toggles on or off (e.g. customer_reply_alerts to text the owner the moment a client texts the business). Managers and owners only. Booleans only — the alert phone number and email cannot be changed here (dashboard Settings → Notifications). Pass only the toggles the user asked to change.

update_notification_preferences

Update an AiFlow's name and/or definition. A supplied definition REPLACES the whole definition and is validated like create_flow (fetch the current one with get_flow first).

update_flow