Extract LinkedIn Sent Invitations

LinkedIn Sent Invitations Extractor retrieves all sent invitations from your LinkedIn account.

Edges is not related to LinkedIn and is not an official LinkedIn product.

API Endpoint

POST/v1/actions/linkedin-extract-sent-invitations/run/live

Parameters

Request parameters

Integration Parameters

Guide

What Extract LinkedIn Sent Invitations does

Extract LinkedIn Sent Invitations pulls every connection request you have sent from your LinkedIn account, returning each invitation as a structured record with recipient, status, and sent-at timestamp. It runs on the LinkedIn level and turns your outbound invitation activity into a query-able dataset instead of a static inbox view.

The action gives you the visibility you need to audit outreach, track acceptance rates, and decide which pending invitations to withdraw.

How it works

You trigger the action against your connected LinkedIn account, and Edges walks the "Sent" tab of your invitations, page by page, through your authenticated LinkedIn session. Each invitation is returned as a typed record — who you invited, whether it is still pending, and what note you attached if any.

The run executes on Edges infrastructure: browser-less, session-authenticated, and paced against LinkedIn's rate guidance. For accounts with thousands of sent invitations, the extraction runs asynchronously and returns a complete list when it finishes.

When to use Extract LinkedIn Sent Invitations

Reach for this action when you need to audit outbound — which invitations are still open, which never accepted, who never saw a follow-up. It fits the LinkedIn messaging & outreach API use case and plugs into any outbound tracking or inbox-hygiene workflow.

Extract LinkedIn Sent Invitations is typically scheduled — weekly or monthly — so your reporting system always has a fresh view of pending outbound.

Use cases

  • Outreach acceptance rate reporting. Aggregate accepted vs pending over the last 30 days to measure how a new invitation template is performing.
  • Inbox hygiene. Find invitations sent more than 14 days ago that are still pending, then feed them into Withdraw pending LinkedIn invitations (bulk) to clear the queue.
  • Sequence de-duplication. Before firing a new invitation to a prospect, check whether one has already been sent; avoid collisions with your sequencer.
  • Attribution. Join sent invitations against new first-degree connections to know which sequence produced which accepts.
  • Compliance audits. Prove what outbound was sent from a shared account during a period by exporting the sent list into a controlled archive.

Best practices

  • Paginate async for large histories. Accounts with long invitation histories should run the extraction asynchronously. Subscribe to a webhook so your workflow reacts to completion rather than polling.
  • Dedupe on `profileId` before acting. A single recipient can appear with multiple invitations over time — pick the most recent to decide your next move.
  • Pair with withdraw actions. Extract LinkedIn Sent Invitations is the natural prerequisite for Withdraw Invitation or its bulk variant. Identify stale pending invites, then clear them.
  • Respect LinkedIn's invitation cap. LinkedIn limits the number of pending outbound invitations per account. Use this action to measure where you sit before sending more.

Common questions

How many invitations can I extract per run?

The action walks the full sent list exposed to your LinkedIn session, bounded by your optional limit or since filter. Accounts with many sent invitations will run asynchronously.

Does Extract LinkedIn Sent Invitations use my LinkedIn account or a shared pool?

Your account. The sent list is private to the sender, so the extraction must run through your authenticated LinkedIn session. Edges handles the pacing and session management.

Can I chain Extract LinkedIn Sent Invitations with other Edges actions?

Yes. Common chains are Extract LinkedIn Sent Invitations → filter pending > 14 days → [Withdraw Invitation](/actions/linkedin-withdraw-invitation) or Extract LinkedIn Sent Invitations → join with CRM → update outreach status. The output is a plain list of records ready for downstream automation.

Get started

Run Extract LinkedIn Sent Invitations on a schedule from the Edges dashboard, or call it via the Edges API from your outbound reporting pipeline. Browse the full Actions library to pair it with withdraw and messaging actions.

Code Examples

bash
curl -X POST "https://api.edges.run/v1/actions/linkedin-extract-sent-invitations/run/live" \
  -H "X-API-KEY: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
  "identity_ids": [
    "your-identity-uuid"
  ],
  "identity_mode": "direct"
}'

Output Example

[
  {
    "linkedin_invitation_id": "example-123",
    "linkedin_invitation_urn": "example_value",
    "sent_date": "1990-01-01",
    "linkedin_profile_url": "https://www.linkedin.com/in/example-profile",
    "job_title": "Software Engineer at Example Corp",
    "full_name": "John Doe",
    "first_name": "John",
    "last_name": "Doe",
    "sales_navigator_profile_id": "example-123",
    "linkedin_profile_id": 42
  }
]

Explore More Actions

Discover other powerful LinkedIn automation actions in our library.