Introduction
What is Intuned?
Intuned is a platform that enables developers to build and consume browser automations as code. Think of it as a way to turn complex browser interactions into simple, callable functions that can be executed reliably at scale.Mental Model
Imagine you need to automate repetitive browser tasks - like extracting data from websites (scrapers), filling forms, or performing web-based complex multi-step workflows. Intuned provides the infrastructure to:- Organize your automations into projects
- Define these automations as reusable parametrized functions
- Execute them reliably on demand or at a schedule
- Monitor their execution
- Scale from single executions to thousands of runs
The Building Blocks
Projects: Organizing Your Automations
A Project in Intuned is a code project - a self-contained unit that groups related browser automation APIs together. Think of it as you would a software project: all the code, configurations, and resources needed for a specific automation goal. Common project patterns:- A single website scraper
- An integration with a specific platform
- A collection of APIs that work together on related tasks
- Organize code: Share helpers, utilities, and common logic between APIs
- Deploy as a unit: All APIs in a project are deployed together
- Configure settings: Authentication, replication/scale, and other settings are defined at the project level
Project = Related APIs + Shared Code + Configuration → Deployable Unit
APIs: Defining Your Automations
At the heart of Intuned are browser automation APIs - these are functions that:- Accept a browser page object (via Playwright)
- Take parameters to customize the execution
- Return results
API Function = Browser Page + Parameters → Result
The Execution Model
Runs: Executing Your Automations
When you execute a browser automation API, you create a Run. A Run represents a logical execution of your automation that may involve multiple Attempts until it succeeds or exhausts all configurable Attempt numbers. Every Run has:- Parameters: The inputs you provide
- Options/Configs: To control the execution
- Status: Current state (Pending → Success/Failed/Canceled)
- Result: The data returned (if successful)
- Attempts: One or more API executions to complete the logical operation (a retry after a failure as an example)
Attempts: Individual API Executions Within a Run
Browser automation is inherently complex. In many cases, a single Run may require multiple API executions - whether for retries after failures, handling transient issues, or other reasons. These individual executions are called Attempts. Each Run consists of one or more Attempts:- Each Attempt represents one complete execution of your API
- Failed attempts can trigger automatic retries (up to your configured limit)
- Every attempt is tracked separately with its own result, trace, and logs
- Attempts may have pre-execution dependencies (like authentication validation)
Execution Patterns
Runs: Single Executions
Perfect for:- On-demand automations
- Testing and debugging
Jobs: Batched Executions
When you need to:- Run multiple APIs in bulk
- Run automations on a schedule
- What automations to run
- When to run them (schedule)
- Where to send the results (sink)
Nested Scheduling
Intuned supports nested scheduling (available in Jobs only) where one API can dynamically expand the JobRun’s workload usingextendPayload
.
How it works:
- An initial API Run (part of a JobRun) decides what else needs to be run as part of the same JobRun
- It calls
extendPayload
to add new payloads to the active running JobRun - The JobRun automatically executes these newly added payloads
- First API: finds all product pages that need to be scraped
- Uses
extendPayload
to expand the payload of the JobRun - Extended APIs: Runs and extracts each product details from product pages
Building Automations
Online IDE
Coming Soon!CLI (Local Development)
Coming Soon!Monitoring
Execution Records and Traces
Every execution in Intuned creates comprehensive records for debugging and monitoring: Run Records - Complete history of each API execution:- Input parameters used
- Final status and result
- All Attempt records
- Execution timeline
- Link to parent JobRun (if applicable)
- Link to AuthSession (if applicable)
- Browser trace for visibility
- Logs for debugging
- Exact error details if failed
- Timing information
Usage Monitoring and Alerting
Coming Soon!Additional Platform Capabilities
AuthSessions: Authentication Support
Intuned supports authenticated browser automations for scenarios when you need to:- Log into websites before automating
- Maintain user sessions across multiple runs