> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# LinkedIn company follower invitations

> Check a managed company Page’s invitation allowance and invite specific people to follow it.

Ask Connie to check how many invitations a company Page can send, or invite
specific people to follow it. These tools are available in AI Chat and authorized
MCP/ChatGPT connections when enabled for your workspace. They are unavailable in
Workflow Actions, Workflow Agents, Records columns and programs.

In a workspace with agents and rooms, ask an agent instead: message it in its DM or in a room.

## Choose the account, Page and people

Start with **List connected accounts**, then **List LinkedIn Managed Pages**.
Choose the connected LinkedIn Classic account and a Page it currently administers.
Connie asks you to clarify ambiguous choices. A public company profile does not
grant permission to act for that company.

**Read LinkedIn Company Invitation Allowance** returns LinkedIn’s remaining
invitation allowance, grant on reset and next reset date. These are LinkedIn Page
invitations, separate from Connie credits. Zero means LinkedIn supplied a zero
balance. Unknown, restricted and failed reads do not establish a zero balance.

For **Invite LinkedIn Company Followers**, select 1–20 specific people using the
existing profile readers, then resolve their first-degree identity with
**Read LinkedIn network**, using `relationship: connections`. Match the chosen
profile URL; clarify ambiguous names. Copy `providerId` to recipient `id` and
`displayName` to recipient `name`, plus the complete Page binding returned by the
managed Pages reader. MCP’s `accountRef` belongs in the connection envelope. Do not substitute a
person’s name alone, a company identifier, a Connie Record ID or a Sales Navigator
identifier. Connie checks current account access, Page administration and each
person’s identity and unblocked first-degree connection before sending.

## Approve only the selected invitations

The send approval names the account, Page and every selected person. Cancel or
Escape sends nothing. Permission for another action or a broader saved tool grant
does not approve a different Page or recipient scope. LinkedIn’s allowance must
cover the unsent scope; Connie does not silently choose a smaller group.

LinkedIn decides final Page-specific eligibility, including whether an invitation
can still be sent. An already following or previously invited person may be
rejected. Invitation allowance can change between reading it and sending.

## Understand results and retries

Each selected person has an **accepted**, **rejected**, **uncertain** or
**not sent** result. A mixed result is partial. Accepted means LinkedIn
acknowledged an invitation; it does **not** mean the person became a follower.

If a send becomes uncertain, Connie stops remaining invitations. It also stops
after an account/provider refusal, rate limit, cancellation or receipt failure,
while preserving earlier results. Do not automatically resend an uncertain
invitation: LinkedIn may already have accepted it. Check LinkedIn before deciding
what to do next. A new invocation key or overlapping selection does not bypass
the retained invitation receipt. Keep the same host idempotency key for a
transport retry; people marked not sent require a new explicit decision.

Connie’s configured tool price and actual usage are accounted for separately
from LinkedIn’s invitation allowance. No automatic campaign, new attachment,
company publishing, commenting, reaction or Inbox company-context capability is
included.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.