Apify collects website data without custom code through prebuilt applications called Actors. In the Google Maps example, a search for coffee shops in Houston, Texas, produces structured business information, including phone numbers and street addresses.
The same platform supports other data-collection tasks, including product research and social media scraping. The process starts with choosing an Actor and configuring the information it should collect.
What Apify Actors Do
Apify is a platform for collecting website information and automating online tasks. Instead of manually copying individual records, an Actor handles a defined task according to its inputs.
The Apify Store contains these applications. Examples include a TikTok scraper, an Instagram scraper, and a Google Maps scraper. Each targets a different source or type of information.
This distinction matters because the tutorial uses an existing Actor rather than building a scraper. The work involves selecting an application, entering search details, and running it. Writing a custom script isn’t part of that process.
Potential outputs include product information, business leads, general website data, and social media content. What an Actor collects depends on its purpose and configuration.
Finding the Store and Results in Apify Console
Apify supports sign-in through a Google account or a regular account. After signing in, Go to console opens the dashboard.
The dashboard displays account usage and resource information, including RAM, a usage limit, and its reset date. It also provides access to the Store, Actors, Storage, and Schedules.
Browsing the Apify Store
The Store groups Actors into categories such as social media and e-commerce. Filters help narrow the selection by pricing model, usage, and developer, including whether Apify or a community developer maintains the Actor.
The Actors area also provides access to Store applications and an account’s own Actors. This walkthrough stays with an existing Store application.
Locating stored data
Storage holds the results of scraping runs. These results are structured datasets rather than information that must be copied out of each source page individually.
Stored data can be exported in formats such as JSON, CSV, and Excel. That makes the dataset available outside the console after the collection task finishes.
Choosing a Google Maps Scraper
The example begins with a search for “Google Maps scraper” in the Apify Store. The selected Actor collects business information that would otherwise require opening and copying individual listings.
An Actor’s page contains its description, README, pricing information, and input details. The description and README explain the task it performs and how its settings work.
Pricing deserves separate attention because different Actors use different charging models. Apify’s Actors in Store documentation identifies the Pricing tab as the place to inspect an Actor’s events and charges.
An Actor’s listed scraping price doesn’t necessarily cover every optional feature. Additional details, reviews, or images can carry separate charges.
The example includes optional add-ons, but the demonstration proceeds without selecting those extra scraping options.
Configuring the Houston Coffee Shop Search
Selecting Use actor opens the input form. The example search is “coffee shops in Houston, Texas,” with “coffee shops” as the search term and “Houston, Texas” as the location.
This configuration defines both the business type and the geographic area. The Actor then handles the collection task rather than requiring a separate manual search for every business.
The form also includes optional settings:
- Place categories can narrow the type of business, with restaurants shown as one available category.
- Additional place-detail scraping can collect more information about listings.
- Review and image options extend the information gathered beyond the basic business details.
These are configuration choices, not required steps in the example. The run uses the coffee shop search without adding those extra options.
Running the Scraper and Reading Its Output
Save and start launches the configured Actor. Apify displays the run’s status, which changes as the task starts and completes.
In the demonstration, the run succeeds and returns a table of business information. The visible results include phone numbers and street addresses, so the output functions as a business-lead dataset.
The important distinction is between the search input and the resulting records. “Coffee shops” and “Houston, Texas” describe the collection request; the output contains the individual businesses found through that request.
The interface reports whether the run succeeded, while the dataset provides access to the collected information. Those are separate parts of reviewing a completed task.
Sharing, Managing, and Exporting the Dataset
The results can be shared as a dataset with a title and a unique name. The demonstration uses the title “test.”
Access initially remains limited to the account owner. Adding another person’s email address allows that person to access the dataset.
Managing the saved results
The dataset can be previewed in a new tab or reopened through Storage. Its actions also include renaming and deleting it.
These controls keep the collected results accessible after leaving the run page. Sharing access doesn’t require exporting a separate file first.
Choosing an export format
The Export menu offers CSV, XML, Excel, JSON, RSS, HTML table, and JSONL.
The choice changes the output format rather than the search that produced the data. A completed run can therefore support different export needs without manually copying its records into another document.
Scheduling the Actor to Run Automatically
Apify’s Schedules area allows an Actor to run on a recurring timetable. The demonstration reuses the Google Maps scraper instead of setting up an unrelated task.
Creating a schedule involves adding the Actor, entering or reusing its input, and saving the configuration. More than one Actor can be associated with a schedule. Apify’s scheduling documentation specifies a maximum of 10 Actors and 10 Actor tasks per schedule.
Setting the timing
The schedule interface includes cron expressions and help explaining them. It also provides a time-zone setting.
The available timing patterns include hourly, daily, and weekly runs. After the Actor and timing are configured, the schedule can be enabled. The interface also provides a control to run it.
This adds recurring execution to the same collection process used for the initial search. The Actor still needs its inputs; the schedule determines when it runs.
Understanding Plans and Actor Costs
The plan comparison shown includes Free, Starter, Scale, and Business. The account used for the demonstration is on the Free plan.
Paid plans provide more resources, including RAM and concurrent runs. The discussion also mentions personal technical training available through a subscription.
Platform plans and Actor charges are separate considerations. A subscription determines access to platform resources, while the selected Actor has its own pricing model and optional features.
Apify’s Actor pricing and costs documentation describes how Actor pricing relates to platform usage. The practical point is that the account plan alone doesn’t explain the cost of every scraping task.
For the Google Maps example, the relevant cost details sit on the Actor’s page, alongside the available add-ons. No single price applies to every application in the Store.
Who Apify Is For
The audiences discussed include content creators, marketers, researchers, developers, and people building AI automations. Their reasons for collecting data differ, but they use the same basic platform components.
Content creators can gather public information. Businesses can collect information for competitor research. Developers and automation builders can use collected data within broader workflows.
The Google Maps example demonstrates one narrower use: collecting local business information in a structured form. It doesn’t build a complete sales system or an AI application. It establishes the data-collection step that those other projects may use.
Connecting Apify to Other Applications
Apify also provides API and integration settings for connecting the platform with other software.
The API area is accessible through the platform’s integration options or through Settings, under API and integrations. An account can create an API token for a third-party application.
Account-level integrations named in the walkthrough include Gmail, Google Drive, GitHub, GitLab, and Slack. These connection options extend the workflow beyond a downloaded dataset.
The walkthrough shows where those controls are located, but it doesn’t build a complete integration with any of those services. Its focus remains on finding the connection settings and creating API access.
How Browse AI’s Approach Differs
Another no-code approach appears in Browse AI’s website scraping tools. Its workflow starts with a webpage URL, after which the system proposes a data structure for review and customization.
Browse AI also offers prebuilt robots, including tools for Google Maps business listings. Its export and integration options include CSV, JSON, Google Sheets, and Airtable.
The distinction is in the setup described here. The Apify demonstration begins with a task-specific Actor from the Store, then supplies its search inputs. Browse AI also supports defining a collection task around a webpage and reviewing the columns it proposes. Its robots and integration options are separate products, not features of Apify.
A Completed Search Becomes a Reusable Dataset
The Houston coffee shop example shows the core Apify workflow: configure an existing Actor, run the search, and retain the results as a structured dataset. Phone numbers and addresses become available without copying each listing manually.
Sharing and exports make that dataset usable outside the run page. Scheduling adds recurring collection, while API settings provide a separate route into other applications. The demonstrated result is a repeatable data-collection task with saved inputs and accessible output.