What it is.
A form trigger takes a role, a city, and a country. Bright Data's Dataset API returns recent job posts, a Code node cleans the results, and Google Sheets stores them.
A company hiring a demand gen manager has a budget line and a gap, which is a better reason to reach out than a firmographic match.
What you get.
- A form you fill with role, city, and country to start a run.
- Recent LinkedIn job posts returned through Bright Data's Dataset API.
- A Code node that cleans the raw results before they land anywhere.
- A Google Sheet of postings you can score and route by hand.
How to set it up.
Add your Bright Data API key to the HTTP Request node headers as a bearer token.
Connect Google Sheets over OAuth2 and give the workflow read and write access to one sheet.
Submit the form with a single role and one city first, so you can read the output before scaling.
Check the Wait node timing, since the Dataset API returns results asynchronously.
Decide which roles count as a signal for you, because hiring a CFO and hiring an SDR mean different things.
Route the sheet into your enrichment step, and keep the job title on the record as the reason for the touch.
Use cases
Treat a job post as intent
Fill the form with a role and city and read back who is hiring for it.
Time an outbound push
Reach the company while the role is still open.
Build a territory list
Run the search per market and keep the results as an account list.
Best for
Selling into a named function
If you sell to marketing, a company hiring marketers is a company with budget and a gap.
Timing an outbound touch
A job post carries a date, so you know the pain is current.
Building a territory list
Filtering by city and country produces a list you can hand to one rep.