Workflow overview
1
Build
Start from a URL, template, or custom task. Select the data fields you want and define actions such as clicking, scrolling, pagination, and opening detail pages.
2
Test
Run a small sample to confirm that Octoparse captures the right fields, records, and page sequence.
3
Run
Execute the task locally for testing or in the cloud for scheduled, unattended, and larger-scale extraction.
4
Export
Send the extracted results to files, spreadsheets, databases, cloud storage, or other connected systems.
Build the task
A task defines how Octoparse interacts with a website. You can build a task by:- Using a template
- Letting Auto-detect identify page data automatically
- Selecting elements manually in the no-code builder
- Adding actions such as click, scroll, loop, pagination, and wait
- Refining field values before export
Test the extraction logic
Before running a task at scale, test a small sample. Check whether:Run locally or in the cloud
Octoparse supports different run options depending on the task and your plan.
The best option depends on the website, task complexity, required frequency, and whether the task needs to keep running when your computer is off.
Export the data
After a task runs, Octoparse stores the extracted results as structured records. Common export destinations include:- CSV
- Excel
- JSON
- HTML
- XML
- Google Sheets
- Databases
- Cloud storage
Related pages
Local vs cloud extraction
Compare run environments and choose the right execution mode.
Export formats
Learn which output formats Octoparse supports.