Sales agents for LinkedIn

Budget check, one search, dedupe against the sender's existing connections, research the shortlist, draft an opener each, write them to a file, and stop. The workflow has no send step and the endpoint exposes no tool that could add one.

Performed by a workflow — a sequence of steps, not a single call. · Human approves

How many LinkedIn tool calls this workspace has made this month, broken down by tool, plus the rate limit in force. The call an agent makes to pace itself instead of discovering the limit by hitting it.

Runs on get_usage · Read only

Writes an opener grounded in a cited line from the person's profile or a post, in the project's voice, under LinkedIn's 300-character invitation-note limit. It produces text in a file. Nothing in the kit can send it.

Performed by a skill — instructions your AI client follows. · Human approves

Writes the next message in a thread from what the person actually replied, including the version that says nothing further is coming. It drafts; a person decides whether it goes.

Performed by a skill — instructions your AI client follows. · Human approves

Intersects the sending account's first-degree connections with a target's company to tell you whether there is an introduction to ask for. It answers from the sender's network only; it cannot see anybody else's connections.

Performed by a skill — instructions your AI client follows. · Read only

Runs an ICP description through a connected account's LinkedIn search and returns up to 50 profiles per call. Profiles LinkedIn masks as "LinkedIn Member" because they are out of network are dropped rather than returned with a blank name. Typed Sales Navigator filters are used only when the account has a Navigator seat; otherwise every criterion is folded into one keyword string.

Runs on search_linkedin_people · Your LinkedIn session

First-degree connections of the connected sender account, up to two hundred per call. It is that account's network, not the network of whoever is signed into the app — which is exactly the distinction that matters when the sender is a dedicated account.

Runs on list_linkedin_connections · Your LinkedIn session

Resolve the profile, read it, read up to ten of their posts, check for a warm path, and produce a dossier with the calls that produced each claim listed underneath it. Four LinkedIn calls per person, and the workflow says so before it starts.

Performed by a workflow — a sequence of steps, not a single call. · Your LinkedIn session

Check the tool list, name the account being acted as, read the remaining budget, run one small search, read three profiles, hand back one brief, stop. The shortest sequence that produces something real.

Performed by a workflow — a sequence of steps, not a single call. · Your LinkedIn session

Every campaign in the workspace with its live funnel counters — invited, connected, replied — and the two rates already rounded to whole percentages.

Runs on list_campaigns · Read only

The lead lists and the leads in them, with whatever enrichment was stored at import. The whole set comes back in one payload: there is no paging or filter argument yet, so a large workspace returns a large response.

Runs on list_leads · Read only

One call returns identity, current role and the date it started, follower count, the premium flag and the latest post. Every enrichment field is best-effort: a profile that hides its activity still returns its identity, with the post fields simply absent.

Runs on get_linkedin_profile · Your LinkedIn session

The AI-written replies waiting for a person to press send. An agent can read and summarise this queue; it cannot approve anything in it, and that is deliberate — sending is the one irreversible action in the product.

Runs on list_tasks · Read only

One thread per lead across every sender account, with full message bodies and — once a reply has been classified — its intent. There is no since or limit argument; the whole inbox comes back.

Runs on get_inbox · Read only

Senders, campaigns, leads, invited, connected and replied, counted across the whole workspace. The cheapest way to answer "how is outreach going" without walking every campaign.

Runs on get_stats · Read only

Up to twenty recent posts by one member, newest first, with reposts flagged. An empty array — not an error — is the normal answer for a senior buyer who does not post, and a workflow has to handle that as a case rather than as a failure.

Runs on get_linkedin_posts · Your LinkedIn session

The accounts this workspace can act as, each with status, warm-up stage, how much of today's invite and message budget is spent, and a health score. Reads our own database, so it costs nothing against the LinkedIn rate limit and is the cheapest first call an agent can make.

Runs on list_sender_accounts · Read only

Classifies an inbox into the same seven intents the app itself uses — meeting, interested, question, objection, not_now, not_interested, neutral — so the queue is read in the order that matters instead of newest-first.

Performed by a skill — instructions your AI client follows. · Read only

Converts a written offer and a few existing customers into the arguments search_linkedin_people actually takes — keywords, location, industry, company, exclude_company — and says which of them LinkedIn will treat as a typed filter versus fold into keywords.

Performed by a skill — instructions your AI client follows. · Read only

Compresses a profile and its posts into a one-screen brief in which every claim names the call that produced it. Anything the tools did not return is written as "not visible" rather than inferred, because an invented detail in a first message is worse than a missing one.

Performed by a skill — instructions your AI client follows. · Read only