Networking agents for LinkedIn

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

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

Read the sending account's connections once, triage them against the target by headline, spend profile calls only on the candidates that survive, check what the connector has been posting about, and produce one intro request per real path — plus an explicit "no warm path here" when that is the answer. One connections call for the whole session, then a handful per candidate.

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

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

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

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

list_connections returns a name, a headline and a public identifier — no company field and no location. This is the judgement for working with that: how to read employer and seniority out of headline text, when the headline is too ambiguous to trust, and which candidates are worth spending a profile call on. It exists because the alternative, reading every connection's profile, costs one LinkedIn call each and is how a warm-path check turns into a rate-limit wall.

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

An introduction request is written for the person being asked to spend their reputation, which makes it a different artifact from an opener: it names what you want, why them, and gives them a forwardable paragraph so saying yes costs one click. It also states plainly when the honest answer is not to ask — a connection whose headline is the only evidence of the relationship is not a warm path.

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