Choose a task-specific Actor
Actors define particular collection or processing tasks. Read the Actor’s own documentation instead of assuming all Actors share one input.
Explore reusable data-collection workflows through Apify Actors. Choose an Actor for the task, review its inputs and inspect the resulting dataset before using it in an Agent workflow.
Example input
| Item | Category | Source |
|---|---|---|
| Brightpath | Workflow software | directory-a.example |
| Northstar | Customer operations | directory-b.example |
| Fieldwork | Team collaboration | directory-c.example |
Actors define particular collection or processing tasks. Read the Actor’s own documentation instead of assuming all Actors share one input.
Prepare a bounded URL list, query or other supported input for the chosen Actor.
Inspect field names and incomplete entries before exporting or using the results.
A reviewed dataset can support an Agent’s classification, research or comparison task.
These fields describe the example workflow. The selected service’s documentation defines its actual request and response contract; review that contract before connecting an Agent.
| Example field | Purpose |
|---|---|
actor | The selected task and its documented input contract. |
input | The configuration passed to that Actor. |
run | Information about a particular execution when a real run is performed. |
dataset_items | Records produced by the chosen Actor; fields vary by task. |
Collect a defined directory sample and check that the records fit your comparison criteria.
Design a repeatable input and review process before implementing a scheduled job.
Test one Actor and a small dataset to establish a usable record format for your next step.
Find Apify in the SpringBrand API marketplace and inspect the available listing.
Select an Actor and read its current input, output and usage requirements.
Use a bounded input and clear review criteria. Check the output before passing it to a downstream step.
No. Apify is a platform for Actors that handle different collection and processing tasks. Google Maps Scraper is one separate example.
No. Input requirements and output records belong to each Actor. The sample on this page is a conceptual directory dataset, not an Actor response contract.
Open the marketplace entry, review its provider and supported operation, and check the requirements for your task. Select an Actor and read its current input, output and usage requirements. This page is a catalogue detail preview and does not execute the service.
Open the Apify entry in the API marketplace to review the available service and its requirements.