Website Job Extractor (Browser)

Pricing

Rating

Developer

Actor stats

Categories

Share

Extract job listings from JavaScript-rendered career pages (React, Vue, Angular SPAs) using AI + Playwright.

This is the browser-based companion to the Website Job Extractor (HTTP-only). Use this actor when the HTTP version flags companies with js_rendering_suspected: true.

When to use this actor

• Career pages built with React, Vue, Angular, or other JS frameworks
• Pages that return empty/skeleton HTML without JavaScript execution
• Companies flagged by the HTTP actor's JS-rendering detection
• Auto-chained via enablePlaywrightFallback on the HTTP actor

Use with AI Agents (MCP)

Connect this actor to any MCP-compatible AI client — Claude Desktop, Claude.ai, Cursor, VS Code, LangChain, LlamaIndex, or custom agents.

Apify MCP server URL:

https://mcp.apify.com?tools=santamaria-automations/website-job-extractor-browser

Example prompt once connected:

"Use website-job-extractor-browser to process data with website job extractor browser. Return results as a table."

Clients that support dynamic tool discovery (Claude.ai, VS Code) will receive the full input schema automatically via add-actor.

How it works

1. Playwright renders the full page (waits for network idle + text content)
2. Career page discovery from homepage navigation (same as HTTP actor)
3. ATS detection for 19 systems (Personio, Greenhouse, Softgarden, etc.)
4. LLM extraction using Gemini Flash / Groq / OpenRouter
5. Validation with confidence scoring and deduplication
6. Pagination follow-up for multi-page listings

Same extraction pipeline as the HTTP actor — same output format, same quality.

Input

Same input format as the HTTP actor. Typically auto-chained:

{
"companies":[
{
"company_id":"abc-123",
"company_name":"TechCorp AG",
"website_url":"https://techcorp.ch"
}
],
"llmProvider":"gemini",
"geminiApiKey":"YOUR_KEY"
}

Output

Each job is a dataset item with browser_extraction: true:

{
"company_id":"abc-123",
"company_name":"TechCorp AG",
"title":"Senior Frontend Developer (m/w/d)",
"location":"Zürich",
"employment_type":"Vollzeit",
"department":"Engineering",
"application_url":"https://techcorp.ch/jobs/apply/123",
"confidence":0.85,
"browser_extraction":true,
"extracted_at":"2026-03-09T10:00:00.000Z"
}

Memory requirements

• Minimum: 1024 MB (Playwright + Chrome)
• Recommended: 2048 MB for 5+ companies
• Maximum: 4096 MB

Pricing

Browser-based extraction costs ~2x the HTTP actor due to Chrome overhead:

Auto-chaining

The HTTP actor can automatically trigger this browser actor for JS-flagged companies:

1. Run the HTTP actor with enablePlaywrightFallback: true
2. Companies with js_rendering_suspected are collected
3. A browser actor run starts automatically (fire-and-forget)
4. The browser run ID is saved in the key-value store as BROWSER_FALLBACK_RUN_ID

LLM fallback chain

Like the HTTP actor, this actor supports automatic provider fallback. Just provide API keys for the providers you want to use:

{
"geminiApiKey":"YOUR_GEMINI_KEY",
"llmApiKey":"YOUR_GROQ_KEY",
"openrouterApiKey":"YOUR_OPENROUTER_KEY"
}

The system auto-discovers available providers and builds a fallback chain (e.g. Gemini → Groq → OpenRouter). If one provider's quota runs out, it instantly falls back to the next.

End-to-end pipeline

This actor is part of a 5-actor enrichment suite:

Limitations

• Higher memory usage (~1GB vs ~128MB for HTTP)
• Slower execution (page rendering + wait times)
• Higher cost per result (2x HTTP rates)
• Use the HTTP actor first — only fall back to browser when needed