Kairon CLI

THIS STARTS SENDING MESSAGES TO REAL PEOPLE ON LINKEDIN, and a message already sent cannot be un-sent.

Per-lead slot coverage.

Create a draft campaign: a name and the sending seat (channelAccountId, a connected LinkedIn account in this org — seat_list returns the ones you can pick), and the ICP to gate enrollment on (icpId).

Read ONE campaign completely enough to REBUILD it.

Enroll one person from the campaign's audience now, instead of waiting for tomorrow's batch.

List this org's campaigns, keyset-paginated — { q?, status?, sort?, direction?, cursor?, limit? }.

Pause an active campaign.

READ THE MESSAGE BEFORE YOU ACTIVATE.

Validate and publish the campaign's draft graph.

The operator's Tasks page, as one read: every send booked to fire (autopilot), every manual run waiting for approval (review), every AI draft that errored (failed), and everything already acted on today (done), plus each seat's daily budge…

THIS SENDS THE MESSAGE.

Stop up to 100 enrolled leads: each run ends, anything drafted or booked for them is dropped, and their parked workflow is torn down so no timer fires later.

Read ONE sequence run in full, by an id from campaign_runs.

Cut short the delay step a run is parked on so the sequence carries straight on to its next step.

Read the campaign's sequence runs — one per enrolled lead — keyset-paginated; page with the returned cursor.

Replace the words a drafted or scheduled send will fire with — the edited text is exactly what goes out, never re-written afterwards.

THIS SENDS THE MESSAGE, sooner than anything else would have: it fires this run's next booked send NOW, outside the send window and the usual pacing.

Replace the campaign's editable DRAFT sequence graph IN FULL — this overwrites, it is not a patch.

How a campaign is performing, in one read — and the read before campaign_activate.

Edit a campaign's configuration — any subset of its fields; omitted ones are unchanged.

Copy an earlier published version back into the campaign's editable DRAFT, steps and routing and layout intact — the way to undo an edit that replaced copy someone wrote.

Every version this campaign has published, newest first, plus its unpublished draft — with a line per version saying what it changed (steps added/removed/edited, routing).

List conversations, newest activity first, across every channel that holds them.

Read one conversation's messages, newest first, by the chatId from chat_list — LinkedIn or email.

Remove one checkpoint from a bet’s history.

Fix what one checkpoint says, or the verdict it froze — for a typo or a verdict typed by mistake.

Record a dated verdict on an initiative: what happened, the one thing to do next, and a health of on_track, at_risk or off_track.

The people who follow a LinkedIn company page YOUR seat administers — the second opted-in audience after a newsletter, and often the bigger one.

A page of a COMPANY page's own posts — what a competitor, a partner or a target account publishes under its own name, not what its people post.

What the operator has told Kairon: their competitor and source URLs, and their organization's value proposition, lead magnet and learnings log.

Replace one or more sections of what the operator has told Kairon: competitorUrls, sourceUrls, valueProposition, leadMagnet, learnings.

One product doc in full, as markdown, by a slug from doc_list.

Kairon's product reference — how each part behaves and where it stops.

Takes no flags.

Order a sending domain and its mailboxes.

Ask Instantly whether this domain's MX, SPF, DKIM and DMARC records are set up correctly.

Price a sending domain and its mailboxes.

Check whether Kairon can buy this domain to send from, and what is available instead when it is taken.

Add a mailbox the customer ALREADY owns — on their own domain, in their own Google Workspace or Microsoft account — so Kairon can send from it.

Ask Kairon to set this workspace up for email sending (plan), or to add enrichment credits (credits).

How this workspace sends email: whether it is on Kairon's sending plan, which sending domains it has and what each mailbox is doing (still being created, warming up, sending, or in trouble), how much of the plan is used, how many enrichmen…

Takes no flags.

Start warming up every mailbox on this sending domain.

Forbid contact with 1..1000 people or companies.

Who this organization must never contact — the org-wide suppression list, in two facets: people (named individuals) and companies (the company itself AND everyone who works there).

Stop suppressing one person or one company, by the entry id exclusion_list returned (exper_… on people, excom_… on companies).

Tell Kairon that something went wrong for this user.

Resolve a human-readable Sales Navigator filter value (location, industry, function) to a LinkedIn id, echoing the canonical label so a wrong match is visible.

One axiom in full, as markdown, by a slug from framework_list.

Kairon's go-to-market theory: the standalone truths every playbook rests on, each a slug, an area (belief-system, targeting, outreach, content, loop) and a title that says exactly what is inside.

Takes no flags.

The members of a LinkedIn group, from the group’s own member list — people who joined a community around a topic, which is a targeting fact no search filter can express.

Create an ICP — a target thesis spanning the companies to reach and the people inside them — at version 1.

Soft-delete an ICP.

Read one ICP and its latest (active) version by icpId.

List this org's ICPs, each with its latest (active) version's criteria and conditions.

Takes no flags.

Qualify one LinkedIn person or company against a saved ICP version and PERSIST the verdict: you judge the AI checks, Kairon judges the structured filters and owns the row.

Revise an ICP: mints a new immutable version, which becomes the active one.

Bring an earlier version back by minting a NEW version equal to it, which becomes the one in use straight away — unlike the campaign equivalent, there is no draft to review first, so confirm with the operator before calling.

Every version of this ICP, newest first, with the date and the check counts for each — and which one is in use.

Who this connection acts as: the user, their organization, the seat (seatId plus its state: connected, none, or locked — needs a subscription), linkedin, and capabilities.

Takes no flags.

The users you may act as, each with their organization and whether they have a LinkedIn account connected — you can only act as someone who does.

Act as another user from now on: every later call runs as them, on their LinkedIn seat and their organization.

Go back to being yourself.

Takes no flags.

Remove one initiative from the board.

One initiative whole: the thinking in its body, the campaigns serving it as the campaigns list knows them, and every checkpoint newest-first with the verdict each one froze.

Every initiative in the organization: what is being bet on, its status, the health of its latest checkpoint and how many days old that verdict is, plus the summed funnel of the campaigns serving it.

Write down a bet: a name, the thinking in markdown, and who is accountable for it.

Send an InMail (optional subject) to the person target addresses.

The org-wide outreach funnel over a date window — invites sent → accepted → messages → replied → interested — with the daily activity series and a per-seat breakdown, each seat carrying its campaigns and their acceptance, reply and interes…

The connection requests waiting in your LinkedIn inbox — people who asked to connect with YOU and have not been answered.

Send a LinkedIn connection invitation (optional note) through the caller's account.

Is this company hiring?

Fetch a LinkedIn person OR company through the caller's connected account — whichever the target addresses ({ type, value }: url, public_identifier, or provider_id).

Add members to a list ({ asset, id, items }, up to 500).

Create a named list — the campaign targeting unit.

Soft-delete a list by asset + id: it disappears from list_list with its memberships, the member leads/companies are untouched (they stay in the org pool, in their other lists, with their qualification state intact), and the name is immedia…

One list by asset + id: its name, live member count, created date, and its ordered columns (the list's own custom columns — free-text fields you attach to its members).

Read this org's lists of one asset, keyset-paginated, newest first, each with its live member count.

One keyset page of a list's members.

Judge a list's members against an ICP and return the run that started.

Stop a run that is still going.

How a qualification run is going, or how it ended.

Remove members from a list ({ asset, id, items }).

Write custom-column values on members ALREADY in a list ({ asset, id, items }, ≤500).

Rename a list and/or replace its custom columns ({ asset, id, name, columns? }).

Retract a message YOU sent, addressed by the chatId and message id that chat_messages returns.

Replace the body of a message YOU sent, addressed by the chatId and message id that chat_messages returns.

Send a LinkedIn direct message.

The people who subscribed to YOUR OWN LinkedIn newsletter — the warmest audience LinkedIn holds, since each one read your writing and chose to keep receiving it.

Make one teammate responsible for the named leads or companies.

Where every one of this org's people stands.

Record where people now stand: new, invite_sent, connected, contacted, replied, interested, meeting_booked, won, on_hold, lost, or discarded.

Everyone who commented on or reacted to ONE named post, by its LinkedIn URL — the audience a post already earned, each person carrying HOW they engaged (their comment text, or which reaction), which is the warmest opening line outreach get…

A page of a profile's recent posts (transient — not persisted).

WHY one lead or company carries the verdict it does ({ asset, id }) — the stored scorecard.

Say whether these people are worth reaching out to, in your own judgement, instead of waiting for Kairon to decide.

Classic LinkedIn people search — the door for ONE kind of ask: something measured from the operator themselves.

Search LinkedIn POSTS — what is being said, by whom, when.

Search Sales Navigator over people OR companies — the door for EVERY people and company search, on every seat and with none.

The LinkedIn seats this organization can send FROM — the same list the campaign wizard's sender picker offers, every one connected and ready.

Takes no flags.

Find people by what they DID, not by what their profile says — the behavioural counterpart to search_people and search_sales_navigator.

One playbook in full, as markdown, by a name from skill_list — call that first; an invented name is a 404.

Kairon's playbooks — how to do each job well: onboarding, Sales Navigator, list building, campaigns, writing messages and posts, what to do next.

Takes no flags.

Detach the source from a lead list.

The source attached to a lead list — the recurring feed that makes it a SIGNAL-BASED list, growing itself over time.

Run the source now instead of waiting for its daily run, and return the run that started.

What the source actually did.

Make a lead list SIGNAL-BASED, or change the one it already is: give it an ICP to target and the signals that should feed it.

Removes the tag from the organization AND from every lead and company wearing it, in one act.

Every tag this organization has, with its color.

Takes no flags.

Without id, creates a tag.

Replaces each named subject's WHOLE tag set — so send every tag it should end up with, not just the new one, and send [] to clear it.

Search, in plain words, for a third-party data endpoint Kairon can run for you — data OUTSIDE LinkedIn: tweets by handle, a Google Maps listing, a company's reviews, a person's record at a data broker, and hundreds more.

The full card for one endpoint webdata_find returned, by its provider and endpoint: what it does, the exact input schema webdata_run expects (path, query and body parameters), the provider's price, a link to the provider's own docs, and an…

What THIS organization will pay for one run of an endpoint with exactly this input — the provider's price plus Kairon's margin — and the quoteId that webdata_run requires.

Fetch the outcome of a webdata_run that came back with status other than COMPLETED, FAILED, BLOCKED, STOPPED or TIMED_OUT — a run the provider was still working on when the 60-second wait ended.

Run one endpoint and get its data back.

Change the organization's own display name, exactly as it appears across the Kairon app.

Run one draft past the SAME judge a real send goes through, and get a pass/fail plus a reason for every rule that governs it.

The rules Kairon holds every draft to, in four sections: general (everything it writes), post, comment, dm (one-to-one messages — campaign sends, inbox replies, auto-replies).

Replace the Author's OWN rules for ONE section, whole.

Switch one of Kairon's SHARED rules on or off for this Author, by a key from writing_check_list.