Real Agent Cases

Withdraw about 1,000 old LinkedIn invitations with Perplexity's agent

Posted
by @BenyaminHolley
Last checked
Method:
How we verify

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

FailureThe source says the agent did not get the job done.

What went wrong: Stuck after about 5 withdrawals; the poster switched to a script.

Outcome

Perplexity Pro's agent mode kept getting tripped up by LinkedIn's infinite scroll, and when asked to withdraw invitations it was painfully slow and got stuck after about 5; the poster had Perplexity write a Cursor prompt for a Selenium script instead.

Agent

Perplexity agent mode

Prompt Improved prompt

Strengthened by us to avoid the problem in the source. Not tested by the poster. It doesn't change what happened in the source.

Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing.

Goal: Clean up my pending sent invitations without getting stuck.

Fill in before running: How many are pending, and should any be kept?

What I'll give you:
- Access to my LinkedIn (I'll sign in)
- Any names to keep

Rules:
- Never withdraw anyone on my keep list.
- Start with a batch of 10. If that goes smoothly, continue in batches of 50 and report progress after each batch.
- Keep a list of who was withdrawn.
- If scrolling or a button stops working twice, stop and tell me rather than retrying endlessly.
- If LinkedIn shows a warning or limit, stop for the day instead of continuing.
- If it's too slow, suggest a safer alternative (e.g. doing it in sessions) instead.

Output: A running count withdrawn, the list, and where you stopped.

You'll know it worked when: the count goes down steadily, and I know where it stopped.

Try this in:

ChatGPT Gemini Grok

This prompt has blanks to fill in. We'll copy it instead of filling it in, so you can edit it before you send.

The source used Perplexity agent mode, which can take actions in a browser or app. These are general chat tools, so results may differ, and a normal chat may only give you a plan.

Opens in a new tab. We don't see what you send.

These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.

The prompt they actually used (our rebuild)

The source didn't share its exact prompt, so we wrote this from what it describes.

Go through my sent invitations and click Withdraw on each one.
Optional stronger version

Our rewrite with extra checks. The poster didn't test it.

Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing.

Goal: Withdraw my old pending LinkedIn invitations reliably without getting stuck.

Inputs (fill in or confirm):
- LinkedIn access (I sign in)
- Names to keep
- How old an invite must be to withdraw

Rules:
- Work in batches of 10 and report progress after each batch.
- Re-load the sent-invitations page after each batch.
- If a button stops working twice, stop and suggest a scripted or manual approach.
- Keep a log of withdrawn names.
- Pause if LinkedIn warns you.
- Never withdraw invites to names on my keep list.
- Stop if LinkedIn shows a limit or error and tell me.

What went wrong before, and how to avoid it:
- Last time it stalled after about 5 withdrawals: reload between batches and stop early with an alternative if it stalls.

If you get stuck: If LinkedIn shows a limit warning, stop for the day. If a login, CAPTCHA or two-step code appears, stop and ask me to handle it; never guess or store passwords.

Verify before you finish: Compare the pending count before and after.

Output: Withdrawn count and log.

Done when: invitations are withdrawn steadily without stalling.

Source

https://x.com/BenyaminHolley/status/1971210280395808873

Related cases

  • Organize a messy SEO work folder and rename screenshots with Claude CoworkRecreated promptEvidence: Shown on videoBeginner-friendly

    Claude Cowork asked how the poster wanted 27 unstructured files organized, created analytics-data, blog-posts and screenshots folders, looked at each screenshot and renamed it by content (e.g. feature-text-to-sql-converter.jpg); the poster says it took about 30 seconds.

    Poster says:27 files sorted in about 30 seconds

    Claude Cowork · Ops · Source date:

  • Have Claude Cowork prepare late-invoice reminder drafts every Monday night, with a report of who owes whatRecreated promptEvidence: Described by posterBeginner-friendly

    Michel, in San Diego, works in a tight-margin business with basic back-office software, and sending late-invoice reminders was repetitive manual work. Claude Cowork walked them through setting up an agent that logs in every Monday night, checks overdue accounts receivable and matches customer names against a Google Sheet of contacts. Using Michel's email template, it adds the contact name, invoice number, amount and due date, puts the emails in the Drafts folder and sends Michel a report of which customers were included, what each owes and the totals. Michel reviews the drafts and sends them, saving about an hour every Monday night.

    Claude Cowork · Ops · Source date:

  • Redline a vendor's standard OEM agreement with Claude for the first three rounds, then have a lawyer do the final checkRecreated promptEvidence: Described by poster

    jedberg regularly negotiates OEM agreements with vendors that mostly use the same template and draw the same objections. They tried Claude first, and their lawyer was impressed that it found things the lawyer had missed. jedberg then used Claude to redline that type of contract, and the other side remarked that the lawyer had been surprisingly thorough. The lawyer did the final check and by then basically said it looked good, and jedberg saved a lot of money by doing the first three rounds with Claude.

    Claude · Ops · Source date: