Skip to content

hybrid-automation

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

hybrid-automation

README.md

Hybrid Automation (Python)

Hybrid automation combining Intuned Browser SDK with AI-powered tools like Stagehand and extract_structured_data.

Run on Intuned

Run on Intuned

APIs

API Description
rpa/fill-form RPA automation that fills consultation booking forms. Uses Playwright via Intuned Browser SDK for form fields, falls back to stagehand.page.act() if selectors fail. Verifies success with Playwright, falls back to stagehand.page.extract()
scraper/list E-commerce product list scraping. Uses Intuned Browser SDK for pagination and link extraction with AI-powered adaptability
scraper/details Product details extraction combining SDK methods with extract_structured_data for unstructured fields like descriptions and specifications
crawler/crawl Job board crawler that extracts structured job postings. Uses static Playwright extraction for Lever (jobs.lever.co), AI extraction with extract_structured_data for other boards (Greenhouse, etc.)

Getting started

Install dependencies

uv sync

If the intuned CLI is not installed, install it globally:

npm install -g @intuned/cli

After installing dependencies, intuned command should be available in your environment.

Prepare the project

Before running any API, provision and deploy the project first.

intuned dev provision
intuned dev deploy

Run an API

intuned dev run api rpa/fill-form .parameters/api/rpa/fill-form/default.json
intuned dev run api scraper/list .parameters/api/scraper/list/default.json
intuned dev run api scraper/details .parameters/api/scraper/details/default.json
intuned dev run api crawler/crawl .parameters/api/crawler/crawl/default.json
intuned dev run api crawler/crawl .parameters/api/crawler/crawl/job-posting.json
intuned dev run api crawler/crawl .parameters/api/crawler/crawl/not-lever.json

Project structure

/
├── api/                          # API endpoints
│   ├── rpa/
│   │   └── fill-form.py          # Form filling with Stagehand fallback
│   ├── scraper/
│   │   ├── list.py               # Product list with pagination
│   │   └── details.py            # Product details with AI extraction
│   └── crawler/
│       └── crawl.py              # Job board crawler (hybrid extraction)
├── hooks/
│   └── setup_context.py          # CDP URL setup for Stagehand
├── utils/
│   └── crawler/                  # Crawler utilities
├── intuned-resources/
│   └── jobs/
│       ├── rpa/
│       │   └── fill-form.job.jsonc      # Job for RPA form filling
│       ├── scraper/
│       │   └── list.job.jsonc           # Top-level job example for product list scraping
│       └── crawler/
│           └── crawl.job.jsonc          # Job for job board crawling
├── .parameters/api/              # Test parameters
├── Intuned.jsonc                 # Project config
├── pyproject.toml                # Python dependencies
└── README.md

Key features

  • Best of both worlds: Combines fast, reliable SDK automation with AI adaptability
  • Smart fallbacks: Uses deterministic methods first, falls back to AI when needed
  • Three use cases: RPA form filling, e-commerce scraping, and job board crawling
  • Production ready: Cost-effective primary path with AI safety net for edge cases

Why hybrid?

Approach Pros Cons
Deterministic (Intuned Browser SDK) Fast, reliable, cost-effective Breaks when site structure changes
AI-Driven (Stagehand, extract_structured_data) Adapts to layout changes Slower, less predictable
Hybrid (this example) Best of both worlds Slightly more complex

The hybrid pattern: use Intuned Browser SDK first (fast path), fall back to AI tools when needed.

Related