AI Web Scraping

Apify, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Apify account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Web Scraping
  • Connects with a key
  • 28 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Apify is

Apify is a platform for building, deploying, and managing web scraping and automation tools, known as Actors.

You paste in a key from your own Apify account. It is kept encrypted, and you can withdraw it from inside Apify whenever you like.

How a run works

One message in, the work done in Apify.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Apify. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Apify account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

28 tools it already has

What it can do in Apify

These are the ready-made tools your AI employee already has in Apify. It is not limited to them, but it never has to be taught these.

  • Create ActorTool to create a new actor with specified configuration. use when you need to initialize a fresh actor programmatically before publishing or running it.
  • Create Actor TaskTool to create a new actor task with specified settings. use when you need to configure or schedule recurring actor runs programmatically.
  • Create DatasetTool to create a new dataset. use when you need to initialize or retrieve a dataset by name.
  • Create Task WebhookTool to create a webhook for an actor task. use when you need external notifications about task run events (e.g., completion or failure) in downstream systems.
  • Delete ActorTool to delete an actor permanently. use when you need to remove an actor by its id or username~actorname. confirm before calling.
  • Delete WebhookTool to delete a webhook by its id. use when removing a webhook after confirming the webhook id.
  • Get Actor DetailsTool to get details of a specific actor. use when you need actor metadata by id or username/actorname.
  • Get all webhooksTool to get a list of all webhooks created by the user. use when you need to enumerate webhooks before filtering or maintenance.
  • Get dataset itemsTool to retrieve items from a dataset. use when you need to fetch data from a specified dataset by pagination or filtering. only json format is fully supported.
  • Get Default BuildTool to get the default build for an actor. use after specifying the actor id; optionally wait for the build to finish before returning.
  • Get Key-Value RecordTool to retrieve a record from a key-value store. use when you need to fetch a specific value by key from an apify key-value store.
  • Get list of buildsTool to get a list of builds for a specific actor. use when you need paginated access to an actor’s build (version) history.
  • Get list of runsTool to get a list of runs for a specific actor. use when you need to paginate through runs and optionally filter by status before processing run data.
  • Get list of task runsTool to get a list of runs for a specific actor task. use when you need to paginate through task runs and optionally filter by status.
  • Get list of task webhooksTool to get a list of webhooks for a specific actor task. use when you need to review or paginate webhooks after creating or updating a task.
  • Get list of tasksTool to fetch a paginated list of tasks belonging to the authenticated user. use when you need to browse or sort tasks created by the user.
  • Get logTool to retrieve logs for a specific actor run or build. use after initiating an actor run or build when you need to inspect execution logs.
  • Get OpenAPI DefinitionTool to get the openapi definition for a specific actor build. use when you need the api schema for code generation or analysis.
  • Get Task InputTool to retrieve the input configuration of a specific task. use when you need to inspect stored task input before execution or debugging.
  • Resurrect RunTool to resurrect a finished actor run. use when you need to restart a completed or failed run. deprecated endpoint; may be removed in future.
  • Run Actor AsynchronouslyTool to run a specific actor asynchronously. use when you need to trigger an actor run without waiting for completion and retrieve its run details immediately.
  • Run Actor SyncTool to run a specific actor synchronously with input and return its output record. use when immediate actor results are needed; runs may timeout after 300 seconds.
  • Run Actor Sync & Get Dataset ItemsTool to run an actor synchronously and retrieve its dataset items. use when immediate access to run results is needed.
  • Run Task AsynchronouslyTool to run a specific actor task asynchronously. use when you need to trigger a task run without waiting for completion and immediately retrieve its run details.
  • Store Data in DatasetTool to store data items in a dataset. use after collecting data when you want to batch-append or update items in an existing dataset.
  • Store Data in Key-Value StoreTool to create or update a record in a key-value store. use after you have the store id and record key to persist json data.
  • Update Key-Value StoreTool to update a key-value store's properties. use when renaming or changing access or schema version of the store after confirming the store id.
  • Update Task InputTool to update the input configuration of a specific actor task. use when you need to modify a scheduled tasks input before execution.
Access, and who is in charge of it

You stay the boss of your Apify account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Apify account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Apify is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Apify and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Apify

Can an AI employee really work inside Apify?
Yes. It signs in to your own Apify account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Apify?
No. Nothing moves and nothing is replaced. Your records stay in Apify, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Apify account?
You paste in a key from your own Apify account. It is kept encrypted, and you can withdraw it from inside Apify whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Apify?
It has 28 ready-made tools in Apify today, among them Create Actor, Create Actor Task and Create Dataset. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Apify and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Apify and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Apify?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Apify is written down with what it did and when.