/v1/actions/linkedin-extract-received-invitations/run/liveExtract 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.
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.
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.
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.
Your account. The received-invitations list is private to the recipient, so the extraction runs through your connected LinkedIn session on Edges.
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.
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.
curl -X POST "https://api.edges.run/v1/actions/linkedin-extract-received-invitations/run/live" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct"
}'[
{
"linkedin_invitation_id": "example-123",
"linkedin_invitation_urn": "example_value",
"message": "example_value",
"sent_date": "1990-01-01",
"invitation_secret": "example_value",
"linkedin_profile_handle": "example-123",
"linkedin_profile_url": "https://www.linkedin.com/in/example-profile",
"first_name": "John",
"last_name": "Doe",
"full_name": "John Doe",
"title": "Software Engineer at Example Corp",
"sales_navigator_profile_id": "example-123",
"linkedin_profile_id": 42,
"linkedin_profile_image_url": "https://www.linkedin.com/in/example-profile"
}
]