How does Sendr know when a connection request has been accepted?

When your sequence sends a LinkedIn connection request and then needs to follow up with a message, Sendr must know whether the recipient accepted before firing the next step. How this works depends on which connection action your sequence uses.

If you're using Send Connection

Send Connection listens for a webhook the moment the contact accepts or declines — that's what tells Sendr to move the contact on. There's nothing to configure and nothing to check manually:

• Accepted — the contact moves straight to your next step
• Declined, or no response within your withdrawal timeframe — the request is withdrawn and the contact goes to the "No" branch

This is instant, so your sequence moves as soon as the contact responds rather than waiting for a scheduled check.

If you're using Send Connection (Legacy)

The legacy action doesn't get a webhook, so Sendr needs to check manually. The standard pattern is a Wait step followed by a Connection Check condition:

1. Wait a set number of days after sending the request
2. Check whether the connection was accepted
3. Branch: continue to the message step if connected, or loop back to wait and check again if not

See "Migrate from the legacy LinkedIn connection request to the new Send Connection action" to switch to the newer, faster setup.

What if a request is already pending?

If a contact already has a pending request from you when the sequence tries to send another, Sendr handles this gracefully and does not send a duplicate request. This applies to both Send Connection and the legacy action.