Skip to main content
Question

Field Agent Prompt Help

  • December 11, 2025
  • 1 reply
  • 8 views
Graham Reed
Forum|alt.badge.img+5

A personal project I am working on is to create a curated list of job roles scraped from the likes of LinkedIn and other places. Specifically, Product Operations (I will say for anyone reading - this is NOT for me, but to support my community who are looking for roles). The idea being, my community can see this specific list, and in the future being able to match skills needed with skills the applicants have, to recommended roles directly.

I’m struggling with 2 things:

  1. A suitable prompt that can look at a top-level URL and then go find instances within that URL of job postings (If you know LinkedIn, I can get a URL that has Product Ops as a search marker, but then getting information from that is proving difficult). 
  2. Because the number of results (records) returned is unknown, I’m using a web-table currently to house this - is this the best way, and what can I then automate from that to get it into a table?

My ideal state is to have this run automatically weekly without input from me. 

Hopefully what I am trying to achieve makes sense, and so from there please tell me what I can do to bring this to life better...

That Product Ops Guy

1 reply

TheTimeSavingCo
Forum|alt.badge.img+31

Hm I’d start by testing a non-LinkedIn website first?  LinkedIn’s pretty scrape unfriendly

Might want to look for an API that handles the Linkedin scrape for you and plugging into that instead too

---

For the scraping bit, I’m not sure if it can handle data loaded dynamically with JavaScript?  And so I’d do a GET on the non-LinkedIn URL to see whether the job data shows up in the HTML, and if it does, point the field agent / AI automation action at it to see whether it can grab them

Because the number of results (records) returned is unknown, I’m using a web-table currently to house this - is this the best way, and what can I then automate from that to get it into a table?

Hm I’m not sure we can create / save webtables with automations currently, and so I think I’d try to do an automation on a weekly trigger that does the scrape with a ‘Generate structured data’ action, followed by a repeating group that creates one record per posting

To handle duplicates, I’d keep a “Scraped jobs” table that receives everything from the automation, and then have that feed into a “Consolidated jobs” table where you upsert based on something like job URL

Adam, Airtable Consultant - thetimesaving.company
Terms & ConditionsAccessibility statement