Linked API

Linked API drives a real LinkedIn account through a dedicated cloud browser. Agents send messages and connection requests, search people and companies, sync the inbox and network, and react to new messages and accepted connections while staying inside the account's limits.

Verified 5 triggers 40 actions API key available

Linked API website Capability data verified 2026-08-25

A scheduled campaign run starts against one connected LinkedIn seat

Search People gathers matches inside a single composed workflow definition

Check Connection Status removes anyone already connected or already invited

Get Limit Usage reports how many connection requests the seat has left in the period

The composed run, its match count, and the remaining allowance post to the seat owner

The seat owner releases the run, trims it, or holds it until tomorrow

What This Integration Enables

Linked API drives a real LinkedIn account through a dedicated cloud browser, which means every operation is something a person could have done in the interface. What makes this connector distinct among LinkedIn tools is where the vendor put its effort: more than half the surface is the governance of the seat rather than the messages sent from it. Six operations exist for rate limits alone, with separate per-period allowances for profile views, connection requests, messages, searches, reactions, comments, and posts. Seats, subscription state, hosted sign-in sessions, reconnection links, and a single audited webhook slot all have their own operations. The account staying healthy is treated as the product.

FlowRunner agents work inside that model rather than around it. They read the seat's remaining allowance before a batch instead of after, check an existing relationship before spending an invitation on it, sync the inbox and the network so acceptances and replies arrive as events, and route an expired session to the person who can fix it. The composed run itself, the one call that searches LinkedIn and then acts on every result, is the point where a person still decides. That is the arrangement FlowRunner exists to make routine: agents do the gathering, the filtering, and the accounting, and the decision that puts a named employee's account on the line waits for its owner.

Without FlowRunner

The account is the thing at risk Outreach volume is guessed at, and the account that pays for a bad guess belongs to a named employee

Nobody sees the queue Work is fired at LinkedIn with no view of what is already waiting or what the seat has spent today

An expired session stops a campaign quietly Sending simply ends, and somebody notices days later when replies dry up

With FlowRunner

The allowance is read before the batch Remaining per-category usage is pulled first, so the size of the run is decided against a real number

Composition happens once, deliberately A search and the action taken on every result travel as one run that a person sized and released

A dead session raises its hand Reconnection becomes an event with a link attached, routed to the person who owns the seat

Use Case Scenarios

A campaign sized against the seat, not against the list

The target list is ready in Airtable. Before anything is sent, the agent calls Get Limit Usage and reads what the account has actually spent this period against its connection request, message, and profile view categories. It runs Check Connection Status across the list and drops everyone already connected or holding a pending invitation, because re-inviting them spends the day's allowance and reads as spam. What remains is composed into one workflow: a Search People call whose nested step acts on every result, which costs one place in the account's queue rather than one per person. The seat owner sees the trimmed list, the composed action, and the remaining allowance in Slack before it runs.
Replies become records, in the right order

Sync Inbox and Sync Network run once on the account, which is what makes the event surface work at all. From then on, On Connection Accepted fires when somebody accepts an invitation the seat sent, and On Inbox Message Received fires on each incoming message. The agent matches on the hashed profile URL rather than the public one, because LinkedIn does not always expose the public form. Accepted connections advance the sequence stage in Salesforce. Replies are classified, and anything reading as a request to stop is written to the suppression list first and answered second. Poll Inbox with a since value keeps the sweep incremental rather than a full re-read.
The seat that stopped working, handled the same day

On Account Reconnection Required fires when a connected account's LinkedIn session expires. Until somebody re-authorizes it, every workflow queued against that seat stays pending and the campaign stops without an error anywhere. The agent responds by calling Create Reconnection Session, which returns a link to Linked API's own hosted sign-in page, and sends it directly to the person who owns the seat with the count of workflows currently parked behind it. Get Connection Session tells the flow whether they actually finished, rather than assuming. The outage is measured in hours instead of in whatever a weekly report eventually shows.

Human-in-Loop Highlight

Execute Workflow is the operation that makes this connector powerful and the one that needs a person. A single call can carry a nested composition where one search runs and every result is acted on. That is the efficient way to use the account's queue. It is also the reason a typo in a search term becomes hundreds of connection requests from a named employee's profile. Workflows run sequentially per account, so that run occupies the only lane the seat has. There is no cancel operation in this connector's action list: once it is queued, it drains. So the agent builds the run and stops. It posts: "Composed run ready on Priya's seat. Search People matched 214 profiles for 'VP Supply Chain, Netherlands', with a nested connection request carrying note variant B. Check Connection Status already removed 38 existing or pending. Get Limit Usage shows 31 of 100 weekly connection requests remaining. Release all 176, trim to the remaining 31, or hold?" The account owner answers. The agent runs exactly what was released, and nothing else reaches the queue.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

40 actions

Workflows

Execute Workflow Starts any Linked API workflow and returns its id rather than its data. The generic form, and the only one that reaches the full action set and the nested composition where a single workflow searches and then acts on every result.
Get Workflow Result Returns a workflow's status and, once it has finished, its result. Reading the pending reason matters as much as the status, because a workflow parked outside the account's working window may not resume until the next working day.

LinkedIn Actions

Send Message Starts a workflow that sends a message to a person, either by profile URL or by replying into a thread an inbox event named. Asynchronous, so it returns a workflow id rather than a delivery confirmation.
Send Connection Request Starts a workflow that invites somebody to connect. Connection requests are the action LinkedIn restricts accounts over, which is why the connector's own limit category exists in front of it.
Check Connection Status Starts a workflow that reports the current relationship with a person. The guard to put ahead of an invitation, because re-inviting someone with a pending request spends allowance and reads as spam.
Search People Starts a workflow that searches LinkedIn for people. Paired with a nested step, one search can act on every result at a cost of one place in the account's queue.
Search Companies Starts a workflow that searches LinkedIn for companies, with results that feed a nested company action in the same run.
Open Person Page Starts a workflow that opens a person's LinkedIn page and reads it. Worth planning for as an outreach signal, since the visit appears in that person's profile views.
Open Company Page Starts a workflow that opens a company page and reads it, with nested retrievals available for employees, decision makers, or posts.

Monitoring and Polling

Sync Inbox Starts a workflow that turns on whole-inbox monitoring for the account. Run once before polling or using the inbox trigger, because without it the inbox looks empty rather than unmonitored.
Sync Network Starts a workflow that turns on connection monitoring. Required before either connection trigger, or a campaign waiting on acceptances waits forever.
Sync Conversation Starts a workflow that syncs one person's conversation history so it can be polled. Per person, where whole-inbox monitoring is usually what a flow wants instead.
Poll Conversations Reads new messages from conversations that have been synced. A direct request rather than a workflow, so it does not queue behind anything.
Poll Inbox Reads messages observed across the whole monitored inbox. A since value turns this into an incremental sweep, and every message carries the thread id a reply needs.
Poll Network Reads connection events on the monitored account. Acceptance of an invitation the seat sent is a different event from a connection formed some other way, and a campaign measuring results wants the first.

Statistics

Get Usage Statistics Returns every action executed in a period with whether it succeeded. The audit view, and how a flow measures its own success rate rather than assuming one. The window it accepts is capped at thirty days.

Accounts

List Accounts Returns the connected LinkedIn accounts with their status and their identification tokens. An account marked as needing reconnection accepts nothing, and its row carries the link that fixes it.
Refresh Account Info Re-reads a connected account's own name, profile URL, avatar, and headline from LinkedIn. It starts a background workflow, so the refreshed values appear on the next listing.
Regenerate Identification Token Issues a new identification token for a connected account. The old one stops working immediately, so every flow configured with it breaks until its connection is updated. The right response to a leaked seat token.
Disconnect Account Disconnects a LinkedIn account from Linked API. The LinkedIn account itself is untouched, but every workflow, monitor, and webhook subscription for that seat stops.

Connection Sessions

Create Connection Session Creates a short-lived link to Linked API's hosted sign-in page, which is what keeps a customer's LinkedIn password out of your product. The completion settings control what the page does afterwards, including success and failure redirects.
Create Reconnection Session Creates a link for re-authorizing an account whose LinkedIn session expired. Where the reconnection trigger should lead, because nothing on that seat runs until someone follows it.
Get Connection Session Returns a session's state, so a flow can find out whether the person actually finished signing in rather than assuming they did.
Cancel Connection Session Invalidates a pending connection link. Worth doing when a link went to the wrong person, since it stays usable otherwise.

Subscription and Seats

Get Subscription Status Returns the Linked API subscription's state. A lapsed subscription refuses every workflow in a way that reads as a broken credential rather than an unpaid bill, so a flow that checks this diagnoses itself.
Get Seats Returns how many seats the subscription has and how many are used. One seat is one connected LinkedIn account.
Set Seats Changes how many seats the subscription pays for, which changes what the organization is billed. Reducing seats below the number of connected accounts freezes the excess rather than refusing the change.

Limits

Get Limits Returns the rate limits configured for an account. These limits are the safety feature, because they exist to keep an automation short of the thresholds LinkedIn restricts accounts over.
Get Default Limits Returns the system defaults that apply to an account with no custom limits. Worth reading before setting a custom one, since the defaults are the vendor's own judgment of what the platform tolerates.
Get Limit Usage Returns how much of each limit the account has spent in the current period. The number that decides whether the next batch is safe to send, and the guard to put in front of a campaign.
Set Limits Sets or updates an account's rate limits, changing only the categories sent. Raising a limit removes the connector's guard, and the ceiling that actually binds is LinkedIn's, which this API cannot see.
Delete Limits Removes named custom limits from an account. The category falls back to the system default rather than becoming unlimited.
Reset Limits To Defaults Puts an account's limits back to the system defaults. The recovery path when a custom limit turned out to be too high and the account started collecting warnings.

Webhooks

Get Webhook Returns the client's active webhook. Linked API allows one per client, so whatever this returns is the only destination events can reach.
Set Webhook Registers the client's single outbound webhook. There is no update, so changing a destination means deleting and setting a new one, and calling this while a trigger is running takes events away from it.
Set Webhook Payload Mode Switches the webhook between inlining a workflow's full result and omitting it. Switching to the lean mode changes what every delivery contains, and a consumer reading the inlined result starts receiving nothing without any error.
Delete Webhook Removes the active webhook and frees the one-per-client slot. Delivery history is kept, pending deliveries are dropped, and any running trigger goes silent.
List Webhook Deliveries Returns recent deliveries with their outcome, attempt count, endpoint status, and last error. Where a silent trigger explains itself.
Replay Webhook Delivery Re-sends a settled delivery reusing the same event id, which makes it a true redelivery for an endpoint that missed one rather than a way to produce a second event.
Send Test Webhook Event Emits a synthetic test event through the real delivery path, so an endpoint can be proven reachable without waiting for a real workflow.

Triggers

5 triggers

Event Triggers

On Workflow Completed Fires when any Linked API workflow finishes, which is the companion to starting one. A workflow can sit queued or parked outside working hours for a long time, so this is better than polling. Whether the result arrives inlined depends on the webhook's payload mode.
On Inbox Message Received Fires when the monitored account receives a LinkedIn message. It requires inbox sync to have run on that account first, or no event is ever produced and the trigger looks broken rather than quiet.
On Connection Accepted Fires when somebody accepts a connection request the monitored account sent. This is the event an outreach sequence actually turns on, and it requires network sync to have run first.
On Connection Request Received Fires when somebody invites the monitored account to connect. The inbound inverse of an acceptance, and useful for routing warm inbound interest to a person rather than a sequence.
On Account Reconnection Required Fires when a connected account's LinkedIn session expires and it can no longer act. The most operationally useful event here, because until someone re-authorizes, every queued workflow stays pending and the campaign stops silently.

Frequently Asked Questions

What can FlowRunner do with Linked API?

FlowRunner agents can run Execute Workflow, Get Workflow Result, and Send Message in Linked API, plus 37 more actions.

Does connecting Linked API to FlowRunner require OAuth?

No. Linked API connects to FlowRunner with an API key, no OAuth flow required.

Can Linked API trigger a FlowRunner workflow automatically?

Yes. Linked API supports 5 triggers that can start a FlowRunner workflow automatically.

Start building with Linked API

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us