How to withdraw pending request

Sending connection requests is only half the job — the ones that never get accepted can quietly pile up and eat into your weekly LinkedIn invitation limit. Flowkon gives you two ways to clean these up automatically, so you always have room to reach new prospects instead of waiting on requests that are unlikely to convert.

Why Withdrawing Pending Requests Matters

LinkedIn caps how many connection requests you can send each week. If your outstanding (pending) requests keep stacking up, you're left with less room to send new ones — even if a chunk of those old requests are never going to be accepted. Withdrawing stale requests regularly keeps your invitation limit free and your outreach moving.

There are two ways to handle this in Flowkon: directly inside a campaign, or workspace-wide from the Settings tab.

Method 1: Add a Withdraw Node in Your Campaign

If you want withdrawal built directly into a specific campaign's flow, you can add a Withdraw node after your connection request step.

Here's how it works:

1. Open your campaign and go to the flow builder.
2. Add a Withdraw node after your connection request step.

3. Set a delay before the withdrawal.

4. If the prospect hasn't accepted the request by the time that delay ends, Flowkon will automatically withdraw it for that campaign.

This is a good option when you want withdrawal logic tied to the specific pacing or strategy of one campaign, rather than applied across your whole workspace.

Method 2: Use the Pending Section in Settings

If you'd rather manage this in one place across all your campaigns, head to the Pending section under Settings.

Here's what you'll find and how to set it up:

1. Go to Settings → Pending.

2. This section displays every pending connection request across all your campaigns in one list.
3. Choose how many days a request should stay pending before it's withdrawn. You can pick from 7, 14, 21, 30, 45, or 60 days.

4. Once set, Flowkon automatically withdraws any request that passes that day limit without being accepted — no need to check back campaign by campaign.
5. You can also manage requests manually from this same list — review who's still pending and withdraw individual requests yourself whenever needed.

Which Method Should You Use?

• Use the Withdraw node if you want campaign-specific control — different campaigns might warrant different waiting periods depending on how warm or cold the audience is.
• Use the Pending section if you want a single, workspace-wide rule applied consistently across every campaign, plus a central place to monitor and manage all pending requests at once.

Both methods can be used together — set a general rule in Settings for overall housekeeping, and use campaign-level Withdraw nodes where a specific campaign needs a different timeline.

Keeping your pending requests in check is a small habit that makes a real difference — it keeps your invitation limit available for prospects who are actually likely to respond.