Nomad Agent / Simple job data

Build job feeds,
alerts, and trackers.

Find job postings from the boards you care about. Keep source facts, original descriptions, and application links ready for your next workflow.

Choose a single source or a bundle. Each Actor is a ready-to-run tool on Apify that returns data you can export or use in your app.

Choose an Actor →Explore the data
  • Source-linked records
  • Single boards & bundles
  • Start with a small run
One simple job rowIllustration

Backend Engineer

Example Studio

Location
Madrid, Spain
Work arrangement
hybrid
Original description
Text + HTML
Application link
Original source URL

A fictional example of the current simple row format. Each Actor’s actual output can differ.

Download JSONExplore the data →

Choose your starting point

One board. Or a broader view.

Pick a focused feed or collect across several sources. Open each Actor for its supported filters and current pricing.

Browse all 38 Actors →

Your first useful run

Choose. Try. Connect.

  1. 01 / Choose

    Pick your sources.

    Use one board for a focused feed, or a bundle for a broader search.

  2. 02 / Try

    Start with a few jobs.

    Open the Actor on Apify, check its input and pricing, and set a small result limit and a cost cap.

  3. 03 / Connect

    Make the data useful.

    Export the results, map them into your app, or connect a spreadsheet. Test the destination before scheduling.

Built around your work

What are you building?

A job feed is a starting point. Connect it to the workflow that matters to you.

01

For your spreadsheet

Keep a useful job tracker.

Keep source IDs, descriptions, and application links together. Update by job identity instead of adding duplicates.

See the workflow →02

For your alerts

Send the jobs you want.

Apply the Actor’s supported filters, then connect a destination you control. Keep a stable scope for recurring searches.

See the workflow →03

For research careers

Bring opportunities together.

Start with a research bundle or an academic board. Read the original requirements, funding, and deadlines.

See the workflow →04

For your coding agent

Give your agent source data.

Inspect the exact Actor schema, request a bounded run, and keep its original job records available.

See the workflow →

Before your first run

A few useful answers.

What does “simple” mean?

Simple readers return source-supplied facts in flat job rows, with original descriptions and links. They do not enrich or translate those rows with AI. Some source-specific products keep their own schemas; check the selected Actor’s Output tab.

How much does a run cost?

Pricing varies by Actor. Check its current Pricing tab, set Maximum cost per run, and start with a small result limit. The number of returned jobs does not necessarily limit scanning or total processing cost.

Can a search return no jobs?

Yes. Filters, source availability, deadlines, and repeat suppression can leave no matching jobs. Read the run summary where available. A successful run does not promise a fixed number of results.

What if I need normalized fields or AI processing?

Visit Job Atlas for separate normalized job Actors and fit scoring. Their inputs, outputs, defaults, and pricing differ from these simple feeds.

Your next workflow

Start with one source.

Try a few results and see how the data fits what you’re building.

Choose an Actor →Read the quickstart