/v1/actions/linkedin-accept-invitation/run/liveAccept Invitation accepts a single pending LinkedIn connection request programmatically, so a new contact lands in your network without you opening the LinkedIn inbox. The action targets one invitation at a time, which makes it a clean primitive to drop into triggered workflows — accept automatically when a lead replies, when a CRM record is created, or when an inbound signal fires.
It runs on the LinkedIn level and uses the session of the LinkedIn account you connect to Edges, so every accept is auditable against that account.
You provide the identifier of the pending invitation (or the inviter's profile), Edges signs the request with your authenticated LinkedIn session, and the invitation is accepted on LinkedIn. The operation is synchronous: by the time the run completes, the invitation has moved from Pending to Accepted and the inviter is now a first-degree connection.
Under the hood the action respects LinkedIn rate guidance — you do not need to throttle client-side. If the invitation has expired, been withdrawn, or is no longer visible, Edges returns a typed error so your workflow can branch cleanly.
Reach for this action when accept-decisions are event-driven rather than batch. Event-driven means a rule, not a human, decides who to accept: a scoring model says "accept inbound from titles matching ICP", a CRM flag says "this lead just converted, accept any pending invites from the buying committee", a calendar trigger says "auto-accept invitations from attendees of last week's webinar".
It pairs naturally with the LinkedIn messaging & outreach API use case — most teams run Accept Invitation as step one, then queue a first-touch message the moment the accept succeeds.
One. This action is designed for per-record triggers. For bulk inbox processing, use the bulk action.
Your LinkedIn account. You connect LinkedIn to Edges once; every accept is executed through that authenticated session and shows up in your account's activity log.
Yes. Most teams chain it immediately into Send LinkedIn Message or Extract LinkedIn Profile to enrich the new connection into their CRM.
Run Accept Invitation from the Edges library, wire it into your CRM or Zapier / Make / n8n flow, or call it directly from the Edges API. Browse the full Actions library to see what you can chain after the accept.
curl -X POST "https://api.edges.run/v1/actions/linkedin-accept-invitation/run/live" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct",
"input": {
"linkedin_invitation_urn": "example_value",
"linkedin_invitation_secret": "example_value",
"custom_data": "example_value"
}
}'[
{
"linkedin_invitation_id": "example-123",
"linkedin_invitation_urn": "example_value"
}
]