Files, fetched and returned.
Plenty of integrations are really "log in, set a date range, click export." The result is a file, and files are awkward for scrapers but native to a browser.
- No credit card required
- Free plan to start
Why file retrieval is awkward
- Downloads need a real browser session, not an HTTP client.
- The export is often generated on demand, after a wait.
- Filenames are inconsistent and unhelpful.
- Getting the bytes into your system is a separate problem.
How Browza handles files
Downloads are captured
Files a run downloads are retained as artifacts and retrievable through the API.
It waits for generation
An export that takes a minute to build is waited on, the way a person would.
Behind a login
Combine with a saved profile to reach documents that require an account.
On a schedule
Month-end collection becomes a scheduled agent rather than a reminder.
How you'd call it
A goal and a schema over HTTP — no selectors to maintain and no browser fleet to run.
“Run a task that exports last month's report, then GET the run's artifacts to pull the file into your system.”
Questions people ask
What file types are supported?
Whatever the site serves — PDFs, CSVs, spreadsheets. They're retained as artifacts.
How do I fetch them?
Through the run's artifacts endpoint, which returns them with their content type.
Is there a size limit?
Artifacts are bounded per workspace plan; the run reports if a download exceeds what's allowed rather than truncating silently.
Related use cases
What will you hand over?
Start with one task. Watch it run, take the wheel whenever you want, and keep the ones that earn their place.