Skip to main content

Workflow Actions

Handle Invitation Received

Accept or decline connection requests automatically — screen prospects against your criteria and respond the moment your workflow decides.

Action Overview

The Handle Invitation Received action accepts or declines a pending connection request received by the connected LinkedIn account. Pair it with the New Invitation Received trigger, and make sure an earlier step finds or creates a contact — the trigger doesn't create one, and this action can't run without a contact in the workflow. Use it to auto-accept requests from qualified prospects, screen them against your criteria, or send a welcome message right after accepting.

⚠️
Important: Requires a Contact This action can't run without a contact in the workflow. If you're chaining it directly from New Invitation Received, add a Find Contact action (by ID) first — creating the contact if none is found.

Use Cases

  • Auto-Accept Qualified Prospects – Screen the sender against your criteria, then accept automatically if they match
  • Screening – Route requests through a qualification step (manual review or an AI check) before deciding
  • Welcome Sequences – Accept the request, then immediately send a welcome or introduction message

Inputs and Required Data

Invitation ID (required) – Identifier of the pending invitation
Example: from the New Invitation Received trigger payload

Shared Secret (required) – Security token required to action the invitation
Example: from the New Invitation Received trigger payload

Action (required) – What to do with the invitation. Supported values:

  • Accept
  • Decline

Obtaining Inputs

  • Invitation ID and Shared Secret both come from the New Invitation Received trigger — see that documentation for a full breakdown of the trigger payload
  • Map both fields directly from the trigger into this action; they can't be obtained any other way

Response

The Handle Invitation Received action returns a simple confirmation and does not require further processing.

Example Response (plain text)

Response: UserInvitationHandled

Workflow Integration

  1. Trigger the Workflow – Start with New Invitation Received
  2. Find or Create the Contact – Add a Find Contact action (by ID) using the Provider ID from the trigger; create the contact if none is found
  3. Screen the Sender – Optionally call Retrieve User Profile, or route through an AI step to categorize the sender
  4. Handle the Invitation – Map Invitation IDShared Secret, and your chosen Action into this step
  5. Follow Up – If accepted, send a welcome message to start the conversation
  • New Invitation Received (trigger) – Provides the Invitation ID and Shared Secret this action requires
  • Retrieve User Profile – Pull the sender's full profile to inform the accept/decline decision
  • Send A Message – Follow up with a welcome message after accepting

Common Errors and Troubleshooting

Action Fails to Run

  • Cause: The Invitation ID or Shared Secret wasn't passed through from the trigger
  • Solution: Map both fields directly from the New Invitation Received trigger payload — both are required and can't be substituted

Workflow Gets Stuck Before This Action

  • Cause: No contact was found or created earlier in the workflow
  • Solution: Add a Find Contact action (by ID) before this step, creating the contact if none is found

Invalid Action Value

  • Cause: A value other than Accept or Decline was provided
  • Solution: Use only the supported values — Accept or Decline

Best Practices

  • Screen before you auto-accept — pull the sender's profile or route through an AI review step so acceptance criteria are consistent
  • Pair with Send A Message to welcome new connections the moment they're accepted, while it's still top of mind for them
  • Decline cleanly rather than ignoring requests that don't match your criteria, so your pending invitations stay manageable