Skip to main content
Question

How to automate data extraction from a web page to a table

  • March 3, 2026
  • 3 replies
  • 25 views

I am trying to create the automation where I put in a link and my agent begins to grab the details on the page and then pass it on down to a table, but my flow won’t do that. It gives me the option to move on to the form and enter the details myself. I don’t want to enter them in myself that’s repetitive. What I want is to automate the process, so it enters does things for me.

3 replies

drtanvisachar
Forum|alt.badge.img+5
  • Zapier Solution Partner
  • March 3, 2026

Hey ​@Dew2 ,

Right now your flow isn’t actually pulling anything from the link. It’s just moving to the next step and waiting for you to type the data in.

If you want it automated, you need a step that actually fetches the page and extracts the info before it goes to your table.

The flow should look like this:

  1. Trigger with the URL.

  2. A step that loads the page (usually a GET request or a “fetch webpage” action).

  3. A step that pulls out the specific details you want from that page.

  4. Map those extracted fields into your table.

If you only pass the link itself, the system has nothing to work with, so it asks you to fill it in manually.

Dr. Tanvi Sachar
Monday Certified Partner, Monday Wizard


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • March 27, 2026

Hey there ​@Dew2 👋 Did you get a chance to try the approach drtanvisachar suggested here?

Let us know if that pointed you in the right direction, or if you're still running into trouble. Want to make sure you're all set! 🙂


Forum|alt.badge.img+1

You’ll usually need one step to read the web page first, and another step to send that data to your table.

So the basic flow is:

URL → web page scraper / HTTP step → extract the fields you want → add row to table

Right now it sounds like your flow is stopping at the form step because it is waiting for manual input instead of pulling the data from the page automatically.

So the fix is: make sure the page data is being captured first, then map those results into your table step.