Clay Icon

Consistently Identical Results from HTTP API Action in Clay Workspace

·
·

I am getting the same results even after running different pages through the HTTP API action

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    This might be happening due to the auto-update settings in your HTTP API action. By default, the column will update whenever you add a new row, but you might be experiencing stale data problems. To resolve this, check these potential solutions: 1. Verify your auto-update settings - you can toggle this off if you don't want automatic updates 2. Make sure you're properly defining the field paths to return in your API response 3. Check if you've enabled the "Remove empty fields" option to prevent sending blank values that might affect your results If you need different results for different pages, ensure that your API endpoint and query parameters are properly configured to reflect the specific page data you're trying to retrieve.

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Was that helpful?

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Looks like you're still looking for help.

    If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

  • Avatar of Bo (.
    Bo (.
    ·
    ·

    Hey Rahul, I'm checking your table right now and it looks like everything was fixed correctly?

  • Avatar of Rahul
    Rahul
    ·
    ·

    I’m using Serper.dev to scrape search results and have set up three different columns in Clay to retrieve results from three different pages. In the Clay column body:

    • Google 1 is set to scrape page 1.

    • Google 2 is set to scrape page 2.

    • Google 3 is set to scrape page 3.

    However, when I run Google 1, it correctly scrapes page 1. But when I run Google 2, it still scrapes page 1 instead of page 2. Similarly, Google 3 should scrape page 3, but it also ends up scraping page 1. Essentially, all columns are fetching only page 1, even though I’ve specified different pages in the column body. I’ve correctly defined the page numbers. , it might be a problem with how serper.dev is processing the input or how Clay is passing the page number to the scraper

  • Avatar of Bo (.
    Bo (.
    ·
    ·

    I recorded this walkthrough video showing exactly how to set this up: https://cln.sh/9jZgkLx6 Let me know if you have any follow-up questions!

  • Avatar of Rahul
    Rahul
    ·
    ·

    Thank you so much! I really appreciate you taking the time to record the walkthrough video. Yes, the issue was due to the incorrect mapping of 'Write to Other Table.' and I have fixed it. Thanks again!