Messaginglinkedin

Withdraw Invitation

Withdraw a pending outbound connection request to free quota and keep your invitation hygiene clean.

POST/v1/actions/linkedin-withdraw-invitation/run/live
Try it liveSee pricing

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

Input

Input parameters

FieldTypeRequired
linkedin_invitation_urnstringyes

The invitation URN. e.g., urn:li:fsd_invitation:1234567890

linkedin_invitation_typestringno

The type of the invitation (e.g., CONNECTION, FOLLOWER, etc.)

Integration

FieldTypeRequired
identity_idsarrayyes

Array of identity UUIDs to use for the action

identity_modestringyes

Mode for identity handling: direct, auto, or managed.

Description

What Withdraw Invitation does

Withdraw Invitation cancels a single pending outbound LinkedIn connection request so you free invitation quota and keep your outbound list clean. You get a confirmed withdrawal attributed to your account plus the metadata of the invitation that was pulled back.

This action runs on the LinkedIn level and is built for sales, recruiting, and growth teams who run disciplined invitation hygiene — withdrawing stale invites to keep the acceptance window fresh.

How it works

You pass the invitation identifier or the recipient's profile URL. Edges signs the withdrawal with your authenticated LinkedIn session, cancels the pending invite on LinkedIn, and returns the receipt. The run is live: by the time the call completes, the invitation has moved from Sent to withdrawn and your outbound quota is released.

Under the hood the action respects LinkedIn's pacing guidance. If the invitation has already been accepted, declined, or expired, Edges returns a typed error so your workflow can branch cleanly.

When to use Withdraw Invitation

Reach for Withdraw Invitation when withdraw decisions are event-driven rather than batch. Event-driven means a rule picks which invite to pull back: a stale-invite job says "anything pending more than 21 days", a CRM flag says "this lead is now a customer, withdraw the outbound invite", an ICP update says "this profile no longer fits, cancel".

It pairs directly with the LinkedIn messaging & outreach API use case — keeping your pending queue clean is how you protect the acceptance rate on the invites that actually matter.

Use cases

  • Stale-invite hygiene. When a pending invite crosses a 21-day age threshold, auto-withdraw to release the quota.
  • ICP change. A lead drops out of your ICP after an enrichment pass; withdraw the pending invite to keep the outbound list tight.
  • Customer cleanup. Once a pending invite turns into a closed-won deal, withdraw the outbound so the record stays clean.
  • Double-invite prevention. Detect a duplicate outbound across two reps and withdraw the older one.
  • Compliance. Withdraw invites to profiles that have flagged they don't want outreach.

Best practices

  • Use the bulk action for mass cleanup. Withdraw Invitation is a per-record primitive. For hundreds or thousands of stale invites, use Withdraw pending LinkedIn invitations (bulk) instead.
  • Run off a stale-age rule. Combine with Extract LinkedIn Sent Invitations to find the invites that need pulling back, then fire Withdraw Invitation per row.
  • Log the withdrawal. Persist withdrawnAt and the days-pending metric so you can tune the acceptance-window threshold over time.
  • Don't thrash invites. Withdrawing an invite and re-sending a week later looks like noise — decide once, then commit.

Common questions

How many invitations can I withdraw per run?

One. Withdraw Invitation is designed for per-record triggers. For bulk cleanup, use the bulk companion action.

Does Withdraw Invitation use my LinkedIn account or a shared pool?

Your LinkedIn account. You connect LinkedIn to Edges once; every withdrawal is executed through that authenticated session and appears in your activity log.

Can I chain Withdraw Invitation with other Edges actions?

Yes. A common chain is Extract LinkedIn Sent Invitations → filter on age → Withdraw Invitation to pull stale rows back, then a downstream job logs the outcome to your CRM.

Get started

Run Withdraw Invitation from the Edges library, wire it into your outbound hygiene job, or call it directly from the Edges API. Browse the full Actions library to see what to chain around the withdrawal.

// Related

Other ways to work with Messaging.

linkedin-accept-invitationAccept InvitationAccept a pending LinkedIn connection invitation so new relationships appear in your network.linkedinlinkedin-accept-invitationsAccept pending LinkedIn invitations (bulk)Accept many pending LinkedIn invitations in one automated run. Use async or scheduled execution to process your inbox at scale and grow your network faster. For a single invitation, use the live Accept LinkedIn invitation action.linkedinlinkedin-archive-messageArchive MessageArchive a LinkedIn conversation thread to tidy your inbox while keeping message history available.linkedinlinkedin-download-attachmentDownload a LinkedIn attachmentDownload a file from a LinkedIn message attachment. The public API uses GET with your identity and the LinkedIn DMS URL; the response is the raw file (binary), suitable for storage, scanning, or further automation.linkedinlinkedin-extract-conversationsExtract LinkedIn ConversationsLinkedIn Conversation Extractor extracts conversations from your LinkedIn account.linkedinlinkedin-extract-messagesExtract LinkedIn MessagesLinkedIn Message Scraper extracts messages from a LinkedIn conversation.linkedin

Try it with 100 free credits.

No card. Copy the snippet, paste your key, hit enter.

Get API key← Back to library