AI Web Scraping

Kadoa, 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 Kadoa 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
  • 27 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 Kadoa is

Kadoa is an API-first platform that enables users to create, manage, and monitor data extraction workflows from unstructured data sources.

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

How a run works

One message in, the work done in Kadoa.

  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 Kadoa. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Kadoa 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.

27 tools it already has

What it can do in Kadoa

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

  • Configure Workflow MonitoringTool to configure monitoring for a workflow to detect data changes by updating workflow metadata. Use after creating or selecting the workflow.
  • Create Advanced WorkflowTool to create an advanced workflow. Use when you need a valid advanced workflow ID before updating steps.
  • Create Notification ChannelTool to create a notification channel for alerts delivery.
  • Create Notification SettingTool to create a notification setting linking channels to events. Use when subscribing workflows or workspace-level notifications to specific events.
  • Create WorkflowTool to create a new workflow in kadoa. Use after configuring URLs and schema or prompt.
  • Enable Data ValidationTool to enable data validation on a specified workflow. Use after creating or updating a workflow to enforce its validation rules.
  • Fetch workflow configurationTool to fetch an advanced workflow’s configuration details. Use when you have a workflow ID and need its steps and metadata.
  • Get all locationsTool to retrieve a list of all available locations. Use when you need to know supported locations before performing location-dependent operations. Use after authenticating with you
  • Get Crawl StatusTool to fetch current status of a crawling session. Use when you need to check progress of a crawl by its session ID.
  • Get Crawled Page ContentTool to retrieve content of a crawled page. Use when you need the HTML or Markdown of a page from a specific crawling session.
  • Get Crawled PagesTool to list pages crawled during a session. Use when you need to paginate through results after starting a crawl session.
  • Get Latest Workflow DataTool to retrieve the most recent data produced by a workflow. Use after confirming workflowId.
  • Get Notification ChannelTool to retrieve details of a specific notification channel. Use when you have a channel's ID and need its configuration.
  • Get Notification Event TypesTool to retrieve supported notification event types. Use when you need to enumerate available notification triggers.
  • Get Notification SettingTool to retrieve a specific notification setting by its identifier. Use when you need to fetch notification configuration details by ID.
  • Get validation configurationTool to retrieve the configuration settings for data validation. Use when you need to inspect validation and linking settings for a specific workflow.
  • Get Workflow Run HistoryTool to fetch workflow run history. Use when you need to retrieve past run records for a workflow after execution.
  • Get Workflow Validation ResultsTool to retrieve the latest validation results for a workflow job. Use after a workflow job completes to inspect its validation outcome.
  • Get WorkflowsTool to retrieve all workflows. Use when you need to list and filter workflows after authenticating.
  • List Validation RulesTool to list all data validation rules with optional pagination and filtering.
  • Post Notification TestTool to send a test notification event. Use when verifying your notification channel configurations.
  • Post Workflow Validation RuleTool to generate and add a new validation rule to a workflow. Use when you need AI-driven data quality rules for a workflow.
  • Run Ad-hoc ExtractionTool to synchronously extract data from a URL using a given template. Use after choosing the schemaId (custom or 'html', 'body', 'markdown').
  • Start Crawl SessionTool to start a web crawling session. Use when you need to initiate a crawl with configuration parameters.
  • Subscribe to Webhook EventsTool to subscribe to specified webhook events. This will create a webhook channel and then create notification settings for the provided events linking that channel.
  • Unsubscribe from Webhook EventsTool to unsubscribe from webhook event notifications by deleting a notification setting. Use when you need to remove an existing notification settings by its ID.
  • Update Notification ChannelTool to update an existing notification channel. Use when you need to modify channel details.
Access, and who is in charge of it

You stay the boss of your Kadoa 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 Kadoa 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 Kadoa 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 Kadoa 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 Kadoa

Can an AI employee really work inside Kadoa?
Yes. It signs in to your own Kadoa 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 Kadoa?
No. Nothing moves and nothing is replaced. Your records stay in Kadoa, 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 Kadoa account?
You paste in a key from your own Kadoa account. It is kept encrypted, and you can withdraw it from inside Kadoa 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 Kadoa?
It has 27 ready-made tools in Kadoa today, among them Configure Workflow Monitoring, Create Advanced Workflow and Create Notification Channel. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Kadoa 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 Kadoa 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 Kadoa?
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 Kadoa is written down with what it did and when.