WorkerKitAI workers for Apify
Ready-made AI workers for Apify: the store's most-used scrapers — Instagram, Google Maps, TikTok, YouTube, X and LinkedIn Jobs — run on a schedule with the results read, summarized and delivered, and every scraper a worker may start granted tool by tool.
- Target Account Hiring Signals
Checks every week which of your target accounts are hiring and logs what the new roles mean on the account's CRM record.
- Competitor Ad Monitor
Reports each week which ads your competitors are running in Meta's public Ad Library: what is new, what they stopped running, and what message they are testing.
- Competitor Social Media Monitor
Checks your named competitors' Instagram, X and YouTube accounts every week and reports which of their posts beat their own normal engagement, with the post cited.
- Google Review Watch
Checks your Google reviews every morning and tells your team which new ones need a reply today.
- Local Lead List Builder
Finds local businesses of one type in one area every week and appends the new ones to a lead spreadsheet.
What is an AI worker for Apify?
An AI worker for Apify is an AI agent scoped to one data-collection job, such as pulling new Google Maps leads for an area every morning or watching a set of Instagram profiles for fresh posts. It runs Apify Actors through your own Apify sign-in, reads the results from each run's dataset, and can start only the scrapers you bind to it — runs are billed by Apify to your account, which is exactly why which scrapers a worker holds is your decision, not a default.
What these workers do
Google Maps lead lists on a schedule
Runs the Google Maps scraper for a search term and area on a cadence, reads the new businesses out of the dataset, and delivers the ones not seen before with phone, website and rating.
Watch Instagram or TikTok accounts
Scrapes a set of profiles on a schedule and reports new posts, follower movement and engagement, so social monitoring stops being a manual rounds-check.
Track competitors in search results
Runs the Google Search scraper for the queries you care about and reports who ranks, what moved, and which ads are showing.
Turn a whole website into an answer
Crawls a site with the content crawler and produces the summary, comparison or knowledge-base entry the pages actually support.
Collect job postings for a market
Scrapes LinkedIn job listings for a search on a schedule and reports new roles, hiring companies and locations — a live read on demand in a market.
How an AI worker runs in Apify
The scrape was never the hard part
Every run costs money, and the worker knows it
Start narrow, with the pinned scrapers
Results live in datasets, and reading them is free of surprises
Some Actors have their own price tag
Apify questions, answered.
Who pays for the scraping runs?
Apify bills your own Apify account for every run a worker starts, mostly per result returned. The free plan includes monthly platform credit, which is enough to trial a scheduled worker; a production schedule usually lands on a paid Apify plan. The worker itself adds nothing to that bill — reading results, runs and logs is free — and because scraper tools are bound one at a time, a worker can only spend on the scrapers you gave it.
Can a worker run any scraper in the Apify Store?
Only if you bind the broad run-anything tool, and that is a deliberate choice rather than the default. The natural shape is narrower: the store's most-used scrapers are individual tools, so a worker holds exactly the ones its job needs — the Google Maps scraper for a leads job, the Instagram scraper for a social job. A worker without the broad tool can search the store and read Actor details, but it cannot start anything you did not grant.
What happens when a scrape takes longer than a minute?
The run keeps going on Apify's side. Starting an Actor returns quickly with a run handle; the worker then checks the run's status and pulls results from the dataset once it finishes. Long site crawls work this way by design, so a big job neither blocks the worker nor times out — and a run that should not have been started can be aborted, which also stops its spend.
Why did a run fail or come back empty?
The run's own log is the first place to look, and workers can read it. Common causes are an input aimed at the wrong thing, a target site that returned nothing for the query, or — for a few store Actors — a rental the account does not have: some Actors need a paid subscription on your Apify account before runs succeed, and that subscription can only be added in your Apify console, never by a worker.
Is scraped personal data protected like everything else?
Yes. Results a worker reads from a dataset pass the same firewall as every other app here: redaction rules and the always-on DLP scan apply to what comes back, every call is logged with the worker, the tool and the time, and rate limits hold. What a worker does with the data downstream is governed by the other tools you bound to it, which is where email and messaging stay under their own rules.
Do we need to set anything up at Apify first?
Just an account. MCP access is available on every Apify account with nothing to switch on, and connecting is a normal sign-in — no API key to find or paste. The one follow-up worth knowing: if a job needs a rental Actor, subscribe to it in your Apify console first, because runs of it fail until the rental exists.
What AI workers can do in Apify
The tools a worker can be granted in Apify once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.
Abort actor run
Stop a running Actor before it finishes. Ends the run's spend; whatever it scraped up to that point stays in its dataset.
X (Twitter) Scraper
Scrape posts from X (Twitter) by search query, profile or URL: text, author and engagement stats. Billed to the connected Apify account.
Google Search Scraper
Scrape Google search result pages for given queries: organic results, ads, people-also-ask and related searches. Billed to the connected Apify account.
Instagram Profile Scraper
Scrape public Instagram profile details — bio, follower counts and recent posts — for a list of usernames. Billed per result to the connected Apify account.
Instagram Scraper
Scrape public Instagram posts, reels, comments, hashtags and places from profile, post or hashtag URLs. Results land in a dataset; each run is billed to the connected Apify account.
RAG Web Browser
Search the web or open one URL and get the page back as clean markdown in a single quick call. The lightweight browse tool for answering a question from a live page; billed to the connected Apify account.
Web Fetch
Fetch a single http(s) URL and return its content. The cheapest read here, for pages that need no browser or search.
Website Content Crawler
Crawl a whole website and extract its page text cleaned for AI use — the bulk read-this-entire-site tool behind summaries and knowledge bases. Crawls can run long and are billed by usage to the connected Apify account.
Call actor
Run any Actor from the Apify Store by name and wait briefly for it to finish. Broad by design: it reaches every Actor the connected account can use, and each run is billed to that account. When a pinned scraper tool covers the job, prefer it over this.
TikTok Scraper
Scrape TikTok profiles, hashtags and videos with their stats: views, likes, shares and comments. Billed to the connected Apify account.
Google Maps Scraper
Extract businesses from Google Maps for a search term and area: name, address, phone, website, rating, review counts and opening hours. The store's most-used Actor; billed to the connected Apify account.
LinkedIn Jobs Scraper
Scrape LinkedIn job listings for a search: title, company, location, posting date and description. Billed to the connected Apify account.
Fetch actor details
Read one Actor's full card: what it does, its input parameters and their types, and its pricing model. Call this before running an unfamiliar Actor so the run's input is right the first time.
Get actor log
Read the log of an Actor run — the place a failed or empty scrape explains itself.
Get actor run
Check an Actor run's status and, once it finishes, the dataset id holding its results. The polling half of any scrape that outlasts the start call's short wait.
Get actor run list
List recent Actor runs in the connected account with status and timestamps, for finding what a worker started earlier or picking up results from a previous schedule.
Get dataset
Read a dataset's metadata — item count and size — before deciding how much of it to pull.
Get dataset items
Page through a run's scraped results with field selection and offset/limit paging. The tool that actually retrieves the data every scrape produces — narrow with fields and page rather than pulling everything at once.
Get dataset list
List datasets in the connected account, newest first, for finding the results of an earlier run without knowing its id.
Get dataset schema
Read the JSON schema of a dataset's items, so a worker knows the field names before pulling data.
Get key value store
Read a key-value store's metadata. Actor runs use these stores for their input, output objects and files kept beside the main dataset.
Get key value store keys
List the keys in a key-value store, to find which record holds a run's output, screenshot or exported file.
Get key value store list
List key-value stores in the connected account, for finding where an earlier run kept its output.
Get key value store record
Read one record from a key-value store, such as a run's OUTPUT object or a stored file.
Search actors
Search the Apify Store's thousands of ready-made scrapers and automations by keyword, returning each Actor's name, what it extracts and how it charges. The starting point when none of the pinned scraper tools covers the job.
YouTube Scraper
Scrape YouTube channels, videos and search results: titles, descriptions, view counts and channel details. Billed to the connected Apify account.