111315755532547057380Q: Output different through Make.com versus within the app
Hi,
I've been playing around with your tool to see if this is something to acquire for our tech stack.
Use case: Extract information from LinkedIn profiles based on URLs as an input.
I have built a workflow (81456962748801372) for this and it works fine in the tool itself. You can see in the logs that it accesses LinkedIn and looks at the profile to extract e.g., the Follower count.
However, when I'm trying to call the workflow in make.com to iterate through a list of say, 100 URLs, it just returns and empty value and the logs show that it's suddently not able to access the LinkedIn profile anymore.
Why?
How can I work around this?
Claire_BrowserAct
Feb 24, 2026A: Hello, thank you for the detailed context. Based on the logs, the root cause is the difference in the entry URL.
When running inside BrowserAct
The workflow is opening a LinkedIn profile URL directly
So the page loads correctly and follower data can be extracted
When triggered via Make
The input URL is a Google search results page
Not the actual LinkedIn profile
The workflow never truly lands on the profile page
So the extraction step returns empty values
This is not a scraping limitation. It is a navigation path issue caused by different entry points.
Two practical workarounds:
Option 1 recommended for stability
Pass the actual LinkedIn profile URLs from Make
Skip the Google results page entirely
No change needed to the existing workflow
Option 2 if you must keep Google URLs
Add a click element step inside the BrowserAct workflow
1 open the Google results page
2 click the first result that leads to the LinkedIn profile
3 run the extraction after the profile page loads
This ensures every run follows the full path open page → enter profile → extract data, which keeps batch runs consistent.
Decision rule
If you already have LinkedIn profile URLs use option 1
If your source is keywords or Google URLs use option 2
You’re also welcome to join our Discord community to get hands-on support and workflow guidance from the team.
Please feel free to send over any additional questions anytime.