Extract Received Invitations
List pending connection invitations you have received to automate accept, decline, or follow-up flows.
/v1/actions/linkedin-extract-received-invitations/run/liveEdges is not related to LinkedIn and is not an official LinkedIn product.
Input
Request parameters
Cursor value obtained from the `X-Pagination-Next` response header of a previous request, used to continue pagination. Cursors expire after 24 hours. If a cursor has expired or is invalid, pagination must be restarted from the beginning.
Maximum number of results per page (read-only; defined by the endpoint, actual count may be lower in some cases like throttling or internal limits).
Integration
Array of identity UUIDs to use for the action
Mode for identity handling: direct, auto, or managed.
Description
What Extract Received Invitations does
Extract Received Invitations lists every pending connection invitation you have received on LinkedIn, returning each as a structured record with inviter, note, and received-at timestamp. It runs on the LinkedIn level and turns your pending-invite inbox into a query-able dataset you can filter, score, and route into accept, decline, or follow-up flows.
Instead of eyeballing the invitations panel, you get every pending request as data — ready for rules-based automation.
How it works
You trigger Extract Received Invitations against your connected LinkedIn account, and Edges walks the Received tab of your invitations through your authenticated LinkedIn session. Each pending invitation is parsed into a typed record with the inviter profile, optional note, and metadata useful for scoring.
The action runs on Edges infrastructure, browser-less and paced against LinkedIn's rate guidance. It returns the current pending-invitations set at the time of the run; for a live view, schedule it to run on a cron and diff against previous results.
When to use Extract Received Invitations
Use this action when who you accept is decided by a rule, not a human — an ICP filter, a fraud filter, a shared-connection threshold. It fits the LinkedIn messaging & outreach API use case and is the standard first step before Accept Invitation or Accept pending LinkedIn invitations (bulk).
Most teams schedule Extract Received Invitations daily, apply scoring, and route each invite into accept, decline, or manual-review queues.
Use cases
- Auto-accept ICP-fit inbound. Score each pending invite by title and company; auto-accept above threshold and auto-decline below.
- Founder-led sales. Pull the daily invitation list, surface only prospects matching your product's ICP, and feed them into an accept-plus-first-touch workflow.
- Recruiter inbox hygiene. Route candidate-fit invites into a screening queue; decline obvious non-matches without ever opening the app.
- Community triage. For a public figure or creator, apply a spam filter (low mutuals, no note, generic headline) to cut inbox noise before manual review.
- Compliance review. Export received invitations with notes attached for a compliance team to audit before anyone accepts.
Best practices
- Schedule, then diff. Run Extract Received Invitations on a cron, store each pending set, and only trigger downstream actions on newly arrived invites.
- Score before you accept. Accepting every inbound hurts your network quality and your LinkedIn recommendations. Always gate on title, company, or mutuals.
- Chain to accept and message. Pair with Accept Invitation followed by Message LinkedIn Profile for a clean connect-and-welcome flow.
- Handle expired invites. Some pending invitations expire silently. If an accept later fails, do not retry forever — mark and move on.
Common questions
How many invitations can I extract per run?
The action walks the full pending Received list exposed to your LinkedIn session, bounded by your optional limit. Inboxes with hundreds of pending invites return the full set; LinkedIn's own cap on visible invitations is the practical ceiling.
Does Extract Received Invitations use my LinkedIn account or a shared pool?
Your account. The received-invitations list is private to the recipient, so the extraction runs through your connected LinkedIn session on Edges.
Can I chain Extract Received Invitations with other Edges actions?
Yes. Typical chains are Extract Received Invitations → score → [Accept Invitation](/actions/linkedin-accept-invitation) → [Message LinkedIn Profile](/actions/linkedin-message-profile) or Extract Received Invitations → audit → decline. The output is a plain list of invitation records ready for any downstream workflow.
Get started
Run Extract Received Invitations on a schedule from the Edges dashboard, or call it from the Edges API as the first step of your inbox automation. Browse the full Actions library to pair it with accept, message, and withdraw actions.
// Related
Other ways to work with Messaging.
Try it with 100 free credits.
No card. Copy the snippet, paste your key, hit enter.