Web Scraper Bugs

Hey guys, love the new updates. I think something with the new update obscures error messages.

Issue 1: Running a web scraper / web scraper agent with a URL - fails but don’t know why. It zooms on my node but no "red error text’. Fails if you use an ‘input’ node or just default value.

Issue 2: Subdomains no longer supported on web scraper nodes?

I get this error when I try to scrape this link: Book Online | Toronto Psychology Clinic

“Invalid URL format. A proper URL must include a scheme (e.g., ‘http’ or ‘https’) as well as a network location (e.g., ‘www.google.com’). Example of a valid URL: ‘https://www.google.com’”

Workbook URL

https://www.gumloop.com/pipeline?workbook_id=1jjinZnAo8vFkYdsss8MFj

Hey @shawnbuilds! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

  1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={your_run_id}&workbook_id={workbook_id}

  2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
    GIF guide

  3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

Hey @shawnbuilds — Noted that the zooming in isn’t immediately clear, but the Web Agent Scraper node requires an Action. In your case it would be “scrape”:

Also, subdomains are supported in both the Web Agent Scraper and Website Scraper nodes.

Here’s the run if you want to take a look.

Let me know if this makes sense and works for you.

Thanks Wasay!

The error was that I didn’t drag the input onto the node. I think the error message here could be clearer! I thought the error was the URL format but the error was that I had to drag the the tag onto the “URL” box due to the new update. I broke a bunch of nodes that way. Probably my fault for skipping the update videos 30sec in though :slight_smile:

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.

Thank you! Noted on the error message, making them more clear across the platform is on the roadmap :slight_smile: