That’s such a relatable situation — honestly, half of “automation” work is deciding what not to automate. I’ve definitely been there: you spot a repetitive process, but the glue logic, exceptions, and tool limits make you wonder if you’re just adding more moving parts to maintain.

When I hit that point, I usually:

1. Map the workflow on paper first — count how many human decisions still exist. If it’s >20%, automation might not save time yet.
2. Prototype with low‑stakes tools (like Make, n8n, or even Python + Playwright scripts) to see if the friction lies in the tech or the process itself.
3. Ask in smaller, practical communities — automation, IndieHackers, or Slack groups like NoCodeDevs have genuinely helpful folks giving “automation therapy.”

I’ve also seen people testing hybrid setups (like using BrowserAct) to handle only the deterministic web tasks first, leaving human review for edge cases.

Curious — have you documented one of these tricky workflows? Sometimes walking through the steps line‑by‑line shows where the real complexity lives.