arbhaveshQ: Two things hit me instantly!
1) The Discord link on your site is broken, so I can’t even find the community to ask for help.
2) I couldn’t find in-app ticketing or live chat support either. Would be super useful to add both.
Now the emergency: I added my custom logins + custom static residential proxy, but BrowserAct still can’t log into my Google account and linkedin. I’m getting a “restricted access” error and I’m stuck.
how can i setup a quick call with a tech support person or help me troubleshoot steps to fix this?
If you have a Loom or YouTube tutorial on login, anti-bot, Cloudflare flows, please share that too.
My use case: scraping LinkedIn profiles via API into n8n. If I store logins in BrowserAct, will it reliably pass human verification and Cloudflare, or should I expect failures? cuz it has failed everytime
Claire_BrowserAct
Feb 8, 2026A: Hi there — really sorry you ran into this, and thanks for flagging it. We’re here and we’ll help you get this working.
About the Discord link: we checked immediately after your message. The links in both the header and footer of the site are working normally. It might have been a temporary loading issue. You can try again or join directly here: https://discord.com/invite/UpnCKd7GaU
Besides Discord, you can also reach us anytime via support@browseract.com
.
In-app ticketing and live chat are absolutely valid suggestions. We agree they’re necessary and they’re already in our roadmap.
Now to the urgent part — login + proxy + restricted access.
When a custom login + static residential proxy still triggers restricted access on Google or LinkedIn, it’s usually related to one of these:
session mismatch
proxy reputation or geo mismatch
account security flags
recent login pattern changes
Cloudflare / human verification sequence timing
Please email us:
your workflow ID
screenshot of the error
whether the proxy is shared or dedicated
We’ll prioritize this and troubleshoot directly on our side.
BrowserAct is designed to automatically handle login flows, anti-bot protection, and Cloudflare challenges, and many users run LinkedIn and Google workflows successfully in production. But platforms like LinkedIn are extremely aggressive with detection, so setup quality matters a lot: proxy stability, session persistence, and workflow timing all affect reliability.
For your use case — LinkedIn profiles → API → n8n — this is a very common production setup. Once login and session are stabilized, workflows can run reliably and feed structured data downstream.
If you’d like faster hands-on help, join Discord and tag the team. We can review your workflow live and guide you step by step.
We’ll stay with you until this is resolved.
Please feel free to send over any additional questions anytime.