Overview
Founders, salespeople, recruiters and job seekers who send connection requests every week end up with a long Sent list: invitations that nobody accepted, weeks or months old. They want to withdraw the old ones, keep the few that still matter, and do it again every week without spending an hour on it.
With Reduck, your AI agent does it for you: it lists your pending invitations, applies your rule, shows you what it will withdraw, and withdraws them after your OK.
Why it's hard
- One button per invitation. LinkedIn's Sent tab (My Network, Manage invitations, Sent) has a Withdraw button and a confirmation for each invitation, and none for all of them.
- The list loads as you scroll. A few invitations appear at a time, so you scroll to the bottom before you reach the oldest ones.
- Pending invitations count against you. LinkedIn's help lists invitations "ignored, left pending, or marked as spam" as a reason it can block you from sending new ones, without a number.
- A withdrawal has a cost. You cannot invite the same person again for up to three weeks, so you do not want to withdraw everything blindly.
How Reduck does it
Your AI agent runs Reduck's LinkedIn scripts in your own Chrome, where you are already signed in. It needs no API key and no extra extension on the LinkedIn page.
- It lists your pending invitations. get_sent_invitations reads your Sent tab, up to 100 invitations by default or more if you ask: each invitation with the name, headline, profile link, your note and how long ago you sent it, and it says whether it read the whole list.
- It applies your rule. "Older than 3 weeks", "no note", "not at a company on my list": you write it in plain words. When the headline is not enough, get_profile opens the profile.
- It shows you the list. You see who stays and who goes before anything changes.
- It withdraws after your OK. withdraw takes each profile link, withdraws the invitation and confirms it. An invitation that was accepted in the meantime is left alone.
What you get: a Sent list with only the invitations you still want, a list of who was withdrawn and when, and a weekly routine your agent runs for you.
How to start
- Create a free account at reduck.ai.
- Install the Reduck extension in Chrome and pair it.
- Connect Reduck to your agent: docs.reduck.ai.
- Ask: "List the LinkedIn connection requests I sent that are still pending and were sent more than {number of weeks} weeks ago. Keep the ones that match this rule: {your rule}. Show me the list of the ones to withdraw, then withdraw them one by one after I say yes."
Tools to bulk withdraw LinkedIn invitations, compared
As each vendor's own page describes it, read on November 16, 2026. "Not documented" means we did not find it on their page.
|
Chooses which ones to withdraw |
Filter by age |
Runs from your AI agent or on a schedule |
Where it runs |
Price |
| Reduck |
Yes, by your own rule in plain words, with the profile if needed |
Yes |
Yes: Claude, ChatGPT or any MCP client, or the CLI |
Your own Chrome |
There is a free tier |
| LinkedIn, by hand |
You click each one |
No |
No |
linkedin.com |
Free |
| Unpend |
You review the list and choose |
Yes, older than a number of days |
Not documented |
Chrome extension, in your browser; at most 25 actions a minute |
Free for 150 actions a month; $4.99 a month, $29.99 a year or $59 once |
| LinkedIn Invite Cleaner |
No, by age only; 2 to 50 per run |
Yes, 1 to 12 months |
No |
Chrome extension (318 users, updated March 11, 2026) |
Free |
| Linked Helper |
Inside its own campaigns ("Cancel sent pending invitations") |
Not documented |
Its own campaigns |
Desktop app on your computer or a server |
From $15 a month, from $8.25 a month on a 12-month term; 14-day trial |
| Console script |
Every invitation loaded on the page |
No |
No |
Your browser's developer console |
Free; breaks when LinkedIn changes the page |
Where Reduck is weaker: it withdraws one invitation per run and asks for your OK, so a backlog of 2,000 invitations takes longer than with an extension built only for this. Your Chrome must be open while it runs.