K3X

Archive (soft-delete) up to 50 active contacts in the connected K3X workspace by `contactIds` from `search_contacts`. Hides them from search while preserving history (reversible via `bulk_restore_contacts`). Returns `archived` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_archive_contacts

Archive (soft-delete) up to 50 active leads in the connected K3X workspace by `leadIds` from `search_leads`. Hides them from search while preserving history (reversible via `bulk_restore_leads`). Returns `archived` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_archive_leads

Change the owners of up to 50 leads in the connected K3X workspace. `leadIds` are ids from `search_leads`. `organizationMembershipIds` are membership UUIDs from `list_organization_members`. `mode` is "set" (replaces owners, [] clears), "add" (appends), or "remove" (drops specified). Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_assign_lead_owner

Create up to 50 contacts (people) in the connected K3X workspace in a single call. Pass `contacts` array with `firstName`, `lastName`, optional `leadId` (to link to a company), `emails`, `phoneNumbers` (E.164), and `timezone`. Best-effort: returns `created` contacts and `skipped` count. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_create_contacts

Create up to 50 leads (companies) in the connected K3X workspace in a single call. Pass `leads` array containing `name` and optional `websites` (full URLs including scheme). Best-effort: returns `created` items and `skipped` count. A created item may carry `failures` listing the parts that did not apply (e.g. "website https://example.com") — the company exists, so add the missing part with `update_lead` rather than creating the company again. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_create_leads

Create up to 50 companies, each with ONE linked contact, in a single call. Pass a `pairs` array; each pair has `company` (name, address, websites, timezone) and `contact` (firstName, lastName, emails, phoneNumbers, timezone). Pairs are processed one by one, best-effort: the company and its contact are created together, then `address` and `websites` are applied as follow-up edits. Returns `created` pairs and a `skipped` count. `skipped` counts only pairs where nothing was created. Each `created` entry carries `lead` ({id, name}, plus `failures` naming any address/website edit that did not apply) and `contact` ({id, firstName, lastName}, or null when the company was saved without its person). When `contact` is null, add the person with `create_contact` using the returned company id; do NOT re-send the pair, which would create a second company. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_create_leads_with_contacts

Remove an email address from up to 50 contacts in the connected K3X workspace. `contactIds` are ids from `search_contacts`. Pass `email` to remove matching email or omit to clear ALL emails from targeted contacts. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_remove_contact_email

Remove a phone number from up to 50 contacts in the connected K3X workspace. `contactIds` are ids from `search_contacts`. Pass `phone` to remove matching phone or omit to clear ALL phone numbers from targeted contacts. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_remove_contact_phone

Remove a website from up to 50 leads in the connected K3X workspace. `leadIds` are ids from `search_leads`. Pass `website` to remove matching URL or omit to clear ALL websites from targeted leads. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_remove_lead_website

Replace an existing email address `from` with a new email `to` across up to 50 contacts in the connected K3X workspace. `contactIds` are ids from `search_contacts`. Only contacts with matching `from` are modified. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_replace_contact_email

Replace an existing phone number `from` with a new phone `to` across up to 50 contacts in the connected K3X workspace. `contactIds` are ids from `search_contacts`. Both `from` and `to` must be in E.164 format. Only contacts with matching `from` are modified. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_replace_contact_phone

Replace an existing website URL `from` with a new URL `to` across up to 50 leads in the connected K3X workspace. `leadIds` are ids from `search_leads`. Only leads with matching `from` are modified. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_replace_lead_website

Restore up to 50 previously archived contacts in the connected K3X workspace by `contactIds`. Find archived contacts with `search_contacts` using `archived: true`. Inverse of `bulk_archive_contacts`: clears the archive flag on each matching contact and records a restore activity. Returns `restored` and `skipped` counts; a contact is skipped when it is not archived or is not in this workspace. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_restore_contacts

Restore up to 50 previously archived leads in the connected K3X workspace by `leadIds`. Find archived leads with `search_leads` using `archived: true`. Inverse of `bulk_archive_leads`: clears the archive flag on each matching lead and records a restore activity. Returns `restored` and `skipped` counts; a lead is skipped when it is not archived, is not in this workspace, or is outside your assigned-records scope. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_restore_leads

Set the SAME custom field value across up to 50 contacts (people) in the connected K3X workspace. `contactIds` are ids from `search_contacts`. `customFieldId` is the UUID of a custom field definition from `list_custom_fields` with recordType "contact". `value` is the value to store. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_set_contact_custom_field

Set the SAME custom field value across up to 50 leads (companies) in the connected K3X workspace. `leadIds` are ids from `search_leads`. `customFieldId` is the UUID of a custom field definition from `list_custom_fields` with recordType "lead". `value` is the value to store. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_set_lead_custom_field

Update up to 50 contacts in the connected K3X workspace in one call. `contactIds` are the `id` values of contacts returned by `search_contacts`. Pass `contactIds` and `timezone` to set the timezone across all targeted contacts. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_update_contacts

Update up to 50 existing leads in the connected K3X workspace in one call. `leadIds` are the `id` values of leads returned by `search_leads`. Pass `leadIds` and either `name` transform steps (append, prepend, replace, trim) or `timezone`. Pass either `name` transforms or `timezone`, not both. Returns `updated` and `skipped` counts. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

bulk_update_leads

Save a new AI agent configuration in the connected K3X workspace. This call only stores the configuration in the workspace. Nothing is executed or delivered by this call; the saved plan runs later, inside K3X, after the agent is activated. `name` is Title Case, 2-5 words (e.g. "Inbound Lead Welcome"). `goal` is a second-person run directive describing what the agent does at run time (e.g. "Send the welcome sequence and offer a call."). `tools` is an optional list of CRM write capability labels (e.g. "createLead", "updateDeal"). Full CRM read access is always granted. The send tools required by email, SMS and meeting steps are added to the saved list automatically. `steps` is the ordered plan (email, sms, meeting, crm_action, push_webhook) the agent will follow when it runs; each step needs a fresh UUID `id`. The push_webhook shape and payload rules are described on the `steps` field. `triggers` lists the record events or time conditions that will start a run; `schedule` is an optional cron expression. Neither is validated against live data at save time. The agent is saved in "draft" state and does nothing until `activate_agent` is called. Constraints are saved empty ({}). Runs execute as the team member who authorized this connection. `handoff` summarizes the conversation in which this agent was designed; it is stored as the opening note of the agent's design chat in K3X so the user can keep refining it there. Record what the user wants, the choices made and why, and every case they ruled out. Returns the new agent's {"id", "name", "state", "webhookEnabled"}. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

create_agent

Create a person (contact) in the connected K3X workspace, optionally linked to a company. Pass `leadId` — the `id` of a lead from `search_leads` or `get_lead_details` — to attach the person to that company, or omit it to create a standalone person, which is fully supported. `emails` and `phoneNumbers` are each stored as separate entries; phone numbers should be E.164 (e.g. "+15551234567"). `lastName` is required and cannot be empty — if the surname is genuinely unknown, ask rather than guess. `timezone` is an optional IANA timezone name (e.g. "America/New_York"). To create a company and its FIRST person together, use `create_lead` with its `contact` field instead: that creates both atomically. Use this tool for the second and subsequent people on a company. Returns the new contact's {"id", "firstName", "lastName"}; use `get_contact_details` or `search_contacts` to read the whole record back. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

create_contact

Create a new custom field DEFINITION (column schema) in the connected K3X workspace. `name` is the display name of the field (e.g. "Industry", "Referral Source"). `type` is one of "text", "url", "number", "currency", "datetime", "single_select", "multi_select". `recordType` is one of "lead" (Companies), "contact" (People), or "deal". Both `type` and `recordType` are immutable after creation. `options` is a required non-empty array of option label strings when `type` is "single_select" or "multi_select" (and invalid for other types). Nothing is deduplicated — call `list_custom_fields` first and reuse an existing field instead of creating a second one with the same name, type and recordType. A field whose name matches an existing one but whose recordType differs is NOT a duplicate. Returns the created custom field definition with its server-assigned `id` and option IDs. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

create_custom_field

Create a new deal in the connected K3X workspace attached to an existing company (lead) and pipeline stage. `name` is the deal name (e.g. "Q3 Expansion", "Enterprise License"). `leadId` is the UUID of an existing lead from `search_leads`. `dealStageId` is the UUID of a pipeline stage from `list_deal_stages`. `amount` is the monetary value of the deal as a non-negative number (or null/omitted). Returns the created deal's {"id", "name"}. Nothing is deduplicated — call `search_deals` first and reuse an existing deal instead of creating a second one with the same name. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

create_deal

Create a new lead (company) in the connected K3X workspace, with as much of its structure as you have. `name` is the company name. `address` is a single free-text postal address. `websites` takes full URLs including the scheme (https://example.com) — a bare domain is rejected. `contact` creates ONE person on the new company in the same call, with their `emails` and `phoneNumbers` — prefer that over creating the company and the person separately, because the two are created together and a bad email or phone rolls both back rather than leaving an empty company behind. Phone numbers should be E.164 (e.g. "+15551234567"). To add more people to the same company afterwards, call `create_contact` with the returned `leadId`. The new lead is owned by the user who authorized this connection. Returns the new lead's {"id", "name"}; use `get_lead_details` or `search_leads` to read the whole record back, including everything written here. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

create_lead

Create a smart view — a saved, filtered tab on the Companies, People or Pipeline page of the connected K3X workspace. `entityType` is "lead" (Companies), "contact" (People) or "deal" (Deals); deal views need deals access on this connection. `name` is the tab label; `description` is one or two plain-language sentences on what the view shows, written for users. `rules` is a flat list of {"field", "operator", "value"} filters combined by `match` ("all" = every rule must hold, "any" = at least one). Every `field` is a `key` from `list_smart_view_available_fields` for the same `entityType`, `operator` is one its `filters` allow, and `value` is typed per that entry's `valueType`: a string, number or boolean, an array of strings for `string_list` / `uuid_list`, an option `id` when `valueOptions` is present, a relative range such as "last_30_days" for `inDateTimeRange`, and omitted for `isNull` / `notNull`. Member ids come from `list_organization_members`, stage ids from `list_deal_stages`, select option ids from `list_custom_fields`. `columns` are column keys in display order (omit for the default columns); `sort` names a sortable key and a direction. At least one of `rules`, `columns` or `sort` is required. `shared` true shows the view to every member; the default is a personal view. Returns the created view's {"id", "name", "entityType", "url"} — share `url` with the user, it opens the page with the view selected. Nothing is deduplicated — call `list_smart_views` first. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

create_smart_view

Permanently delete a smart view from the connected K3X workspace. `smartViewId` is the `id` of a view returned by `list_smart_views`. Only the view's creator or the owner of a personal view can delete it, and default views cannot be deleted. Records in the view are not touched. This is not reversible — confirm with the user before calling it. Returns the deleted view's {"id", "name", "entityType"}. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

delete_smart_view

Fetch the complete definition of a single AI agent in the connected K3X workspace by `agentId`. `agentId` is the `id` of an agent returned by `list_agents` or `create_agent`. Returns the full editable agent definition including name, goal, description, state, triggers, schedule, steps (with their step ids and channel payloads), tools, constraints, and the builder `thread` (with its conversation messages and design context) when one exists. Use this to inspect how an agent is configured, review its design conversation, or to read existing step ids before calling `update_agent`. The inbound webhook URL is never returned over this API. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

get_agent

Fetch the full detail of a single contact (person) in the connected K3X workspace by `contactId`. `contactId` is the `id` of a contact returned by `search_contacts`, `create_contact`, or nested inside a lead. Returns the complete record including first name, last name, timezone, emails and phone numbers (each with its entry id), linked companies (leads), and custom fields. Use this to resolve individual entry ids (such as email or phone entry ids) needed by `update_contact`. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

get_contact_details

Fetch the chronological activity feed for a lead (company) in the connected K3X workspace by `leadId`. `leadId` is the `id` of a lead returned by `search_leads`. Returns timeline items: field edits, contact link/unlink events, deal updates, emails, SMS messages, calls, and meetings. `filter` optionally scopes to a specific channel ("all", "emails", "calls", "sms", "meetings"). The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

get_lead_activity_feed

Fetch the full detail of a single lead (company) in the connected K3X workspace by `leadId`. `leadId` is the `id` of a lead returned by `search_leads`. Returns the complete record including name, address, timezone, websites (each with its entry id), linked contacts/people (with their emails, phone numbers, and ids), deals, owners, and custom fields. The `deals` key is present only when this connection was also granted deals access; when it is absent, that says nothing about whether the lead has deals. Use this to read the full record or resolve individual entry ids (such as `websites[].id` or `contacts[].id`) needed by update tools. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

get_lead_details

Attach an existing contact (person) to an existing lead (company) in the connected K3X workspace so they appear in `lead.contacts[]`. `leadId` is the `id` of a lead from `search_leads` or `create_lead`. `contactId` is the `id` of a contact from `search_contacts` or `create_contact`. Idempotent — re-linking an already-linked pair is safe. Inverse of `unlink_contact_from_lead`. Does not move or copy the contact — the same contact can be linked to multiple leads. Returns {"leadId", "contactId"}. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

link_contact_to_lead

List AI agents in the connected K3X workspace. Filter by lifecycle state ("draft", "active", or "paused") with `state`, or omit to list all agents. Page through larger result sets with `limit` and `skip`. Returns {"total", "items"}: each entry carries the agent id, name, description, goal, state, triggers, webhook status, and timestamps. Use `get_agent` to fetch the full editable plan (steps, tools, constraints). The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

list_agents

List all custom field DEFINITIONS in the connected K3X workspace (not the per-record values). Takes no arguments. Returns each field's `id`, `name`, `type` (text, url, number, currency, datetime, single_select, multi_select), `recordType` ("lead" = Companies, "contact" = People, "deal" = Deals), and `options` array for select fields (null for other types). Each field belongs to exactly ONE record type. Call this before `set_lead_custom_field` or `set_contact_custom_field` to resolve `customFieldId` and check valid option labels/ids and expected types. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

list_custom_fields

List all pipeline stages configured in the connected K3X workspace in display order. Takes no arguments. Returns `stages` where each entry carries `id`, `name`, `order`, and `kind` ("active", "won", or "lost" — use it to tell which stage closes a deal). Use this to discover `stageId` values before calling `create_deal`, `update_deal`, or `move_deal_to_stage`. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

list_deal_stages

List all team members in the connected K3X workspace — each with `membershipId`, `firstName`, `lastName`, `email`, and `role`. Takes no arguments. Use this to discover `membershipId` values for owner filtering (e.g. `ownerMembershipIds` in `search_leads` and `search_contacts`) and owner assignment. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

list_organization_members

List outbound webhook deliveries for an AI agent in the connected K3X workspace. `agentId` is the `id` of an agent returned by `list_agents` or `create_agent`. `status` filters by delivery status: "queued", "delivered", or "failed". Omit for all statuses. Returns the total count and delivery records including destinationUrl, status, payload, errorMessage, deliveredAt, and failedAt. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

list_outbound_deliveries

List the fields a smart view can filter, show as columns, or sort by for one record type in the connected K3X workspace. `entityType` is "lead" (Companies), "contact" (People) or "deal" (Deals); deal fields need deals access on this connection. Returns {"entityType", "fields"}: each field carries its exact `key` (use it verbatim in `create_smart_view`), `name`, `description`, `filters` (each entry lists the `operators` it allows, the `valueType` those operators expect, and `valueOptions` when only listed values are accepted — pass an option's `id` for select custom fields and the string itself for relative date ranges such as "last_7_days"), plus `column` and `sortable` flags for this entity. Fields keyed `lead.*`, `contact.*` and `deal.*` reach related records too, e.g. a contact view can filter on `lead.owners`. Call this before `create_smart_view` so every rule, column and sort uses a key this workspace actually has. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

list_smart_view_available_fields

List the smart views (saved filtered tabs) for one record type in the connected K3X workspace: the shared views every member sees plus the personal views of the authorizing user. `entityType` is "lead" (Companies), "contact" (People) or "deal" (Deals); deal views need deals access on this connection. Returns {"views"}: each view carries `id`, `name`, `description`, `shared`, `isDefault`, its stored `filter`, `columns` and `sort`, and `createdAt`. Views are returned in their tab order. Call this before `create_smart_view` to reuse an existing view instead of creating a duplicate. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

list_smart_views

Move an existing deal to a different pipeline stage in the connected K3X workspace. `dealId` is the UUID of an existing deal from `search_deals` or `create_deal`. `stageId` is the UUID of the target pipeline stage from `list_deal_stages`. Returns {"id", "name", "stageId"}. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

move_deal_to_stage

Pause an active AI agent in the connected K3X workspace by `agentId`. `agentId` is the `id` of an agent returned by `list_agents`. Cancels queued runs and any scheduled emails/SMS messages the agent had armed. Returns {"id", "name", "state": "paused", "webhookEnabled"}. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

pause_agent

Restore a previously archived contact (person) in the connected K3X workspace by `contactId`. `contactId` is the `id` of an archived contact returned by `search_contacts` (with `archived: true`). Makes the contact visible again in searches. Inverse of `archive_contact`. The workspace is fixed by the authorization this connection was granted, so there is no organization parameter.

restore_contact