Integration

Kadoa integration

Kadoa is an AI web-data extraction platform: you describe what to collect from a website and Kadoa builds and runs a scraping workflow for it. With this API an agent can create workflows from natural-language instructions, a schema or a template, run them, read the extracted records and the run history, export a result set to a signed download URL, follow detected data changes, and manage schemas, templates, variables, data quality rules, workflow-to-workflow triggers and notification channels and settings. The Assistant session routes, support tickets, and the routes that answer plain text (pause, schedule and delete a workflow) or stream a file are not exposed. Authentication is the workspace API key (it starts with tk-), generated under Settings, General in Kadoa and sent in the x-api-key header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Kadoa.Built from the 57 Kadoa tools below, on the connection you add once.

What you can do with Kadoa

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Schema, 6 operations

  • create_schemaCreate schemaPOSTCreate a new data schema with specified fields and entity type
  • delete_schemaDelete schemaDELETEDelete a schema and all its revisions
  • get_schemaGet schemaGETRetrieve a specific schema by its unique identifier
  • list_schemasList schemasGETRetrieve all schemas accessible by the authenticated user
  • list_template_schemasList template schemasGETList the schemas linked to a template.
  • update_schemaUpdate schemaPUTUpdate schema metadata or create a new revision with updated fields

Channel, 5 operations

  • create_notification_channelCreate notification channelPOSTCreate a notification channel (email, Slack, webhook or websocket) that notification settings can then deliver to; link it with create_notification_settings.
  • delete_notification_channelDelete notification channelDELETEDelete a notification channel by id.
  • get_notification_channelGet notification channelGETGet one notification channel by id, with its type, configuration and linked notification settings.
  • list_notification_channelsList notification channelsGETList the notification channels (email, Slack, webhook, websocket) set up on the workspace, with the notification settings linked to each.
  • update_notification_channelUpdate notification channelPUTUpdate a notification channel's name, type and configuration.

Settings, 5 operations

  • create_notification_settingsCreate notification settingsPOSTSubscribe notification channels to an event, for one workflow or, without workflowId, for the whole workspace.
  • delete_notification_settingsDelete notification settingsDELETEDelete one set of notification settings by id.
  • get_notification_settingsGet notification settingsGETGet one set of notification settings by id, with its event, workflow and linked channels.
  • list_notification_settingsList notification settingsGETList the notification settings: which event, for which workflow or the whole workspace, goes to which channels.
  • update_notification_settingsUpdate notification settingsPUTUpdate notification settings: the event, the linked channels, or whether they are enabled.

Template, 5 operations

  • create_templateCreate templatePOSTCreate a new template for the team
  • delete_templateDelete templateDELETESoft-delete (archive) a template and cascade-unlink any workflows that referenced it.
  • get_templateGet templateGETRetrieve a template with all its published versions
  • list_templatesList templatesGETList all active templates for the authenticated user's team
  • update_templateUpdate templatePUTUpdate template name or description

Variable, 5 operations

  • create_variableCreate variablePOSTCreate a new key-value variable. Keys must be unique within the team/user scope. Variables can be referenced in workflow prompts using @variableKey syntax.
  • delete_variableDelete variableDELETEPermanently delete a variable by its ID. A secret bound to a connector returns 409 Conflict.
  • get_variableGet variableGETRetrieve a specific variable by its ID.
  • list_variablesList variablesGETRetrieve all variables in the current team/user scope (max 100).
  • update_variableUpdate variablePATCHUpdate an existing variable. At least one field (key, value, or dataType) must be provided.

Trigger, 4 operations

  • create_workflow_triggerCreate workflow triggerPOSTCreate a trigger that starts a target workflow when this source workflow emits an event. Target must share the source's ownership scope and not be a realtime workflow; at most 5 triggers per source.
  • delete_workflow_triggerDelete workflow triggerDELETEDelete a workflow-to-workflow trigger, so the source workflow's event no longer starts the target workflow.
  • list_workflow_triggersList workflow triggersGETList the triggers where this workflow is the source (triggers) and those where it is the target (incoming). A source workflow has at most 5 triggers.
  • update_workflow_triggerUpdate workflow triggerPATCHChange the event that fires a workflow trigger, or enable or disable it.

Workflow, 4 operations

  • create_workflowCreate workflowPOSTCreate a scraping workflow on urls (one website) plus one of: userPrompt (what to extract, in plain words), schemaId, entity with fields, or templateId. Returns the workflowId; then use list_workflow_runs and get_workflow_data.
  • get_workflowGet workflowGETGet a workflow's full configuration and current state by id.
  • list_template_workflowsList template workflowsGETList all workflows created from this template (isOutdated flag is informational-only in v1, applyUpdate is disabled)
  • list_workflowsList workflowsGETList the workflows (scrapers) on the account with their state, paged with skip and limit and searchable by name or id. Use a workflow id with get_workflow_data or run_workflow.

Schema validation rule, 3 operations

  • delete_field_data_quality_rulesDelete field data quality rulesDELETERemove all data quality rules for a single schema field on a workflow. Other fields' rules are left untouched.
  • get_data_quality_rulesGet data quality rulesGETReturns the per-field data quality rules persisted on the workflow. The response is a map keyed by schema field name. A workflow without any rules returns `rules: null`.
  • upsert_data_quality_rulesUpsert data quality rulesPUTPatch-merge a workflow's per-field data quality rules (a map keyed by field name). Sent fields replace their rules, others stay; remove one with delete_field_data_quality_rules. Applies from the next run.

Change, 2 operations

  • get_data_changeGet data changeGETGet one detected data change by id, with the current records, the field-level differences, the summary and the screenshot URLs.
  • list_data_changesList data changesGETList data changes Kadoa detected on monitored workflows, with the changed records, a field-level diff and a one-sentence summary. Filter by workflows and date range.

Event type, 2 operations

  • get_notification_event_typeGet notification event typeGETGet the details of one notification event type.
  • list_notification_event_typesList notification event typesGETList the events Kadoa can notify on (for example workflow_finished, workflow_failed, workflow_data_change), for create_notification_settings.

Apply, 1 operation

  • apply_template_versionApply template versionPOSTApply a template version's config to existing workflows (clone with lineage update)

Connector, 1 operation

  • list_workflow_destinationsList workflow destinationsGETReturns the team's destinations that deliver this workflow after each run. Only deliverable destinations are listed (enabled, verified, not revoked).

Data, 1 operation

  • get_workflow_dataGet workflow dataGETRead the records a workflow extracted, page by page (latest run unless runId is given). Filter, sort, or select rows; for a whole large result set use create_workflow_data_export instead.

Export, 1 operation

  • create_workflow_data_exportCreate workflow data exportGETExport a workflow's full result set as CSV, JSON or Parquet and get a signed download URL (valid until expiresAt) that opens without an API key. Hand the url to the user or a download step.

From workflow, 1 operation

  • create_template_from_workflowCreate template from workflowPOSTExtract a workflow's prompt, schema, validation rules, and notifications into a new template or as a new version of an existing template.

History, 1 operation

  • list_workflow_runsList workflow runsGETList a workflow's runs, newest first, with each run's state, start and finish time, record count and errors. Filter by status or look up one run by runId.

Link, 1 operation

  • link_workflows_to_templateLink workflows to templatePOSTAssociate existing workflows with this template at the latest version. Returns 409 with conflict details if workflows are linked to another template (use force: true to override).

Location, 1 operation

  • list_locationsList locationsGETList the countries a workflow can scrape from (country name and two-letter ISO code), for the location setting of create_workflow.

Metadata, 1 operation

  • update_workflowUpdate workflowPUTUpdate a workflow's settings: URLs, record limit, interval or cron schedules, timezone, name, description, tags, location, monitoring, entity, schema or prompt. Leave out a field to keep its current value.

Preview schema change, 1 operation

  • preview_template_schema_changePreview template schema changePOSTPreview the data a schema change would produce for one linked workflow, without applying the template or running the workflow

Quality metric, 1 operation

  • get_workflow_quality_metricsGet workflow quality metricsGETReturns the data quality metric results for a workflow run, plus the run's total data quality issue count.

Resume, 1 operation

  • resume_workflowResume workflowPUTResume a paused workflow, or resume a workflow left in preview or error state.

Run, 1 operation

  • run_workflowRun workflowPUTStart a run of a workflow now. Runs consume Kadoa credits. Then read progress with list_workflow_runs and the records with get_workflow_data.

Test, 1 operation

  • test_notification_settingsTest notification settingsPOSTSend a test notification with mock data for an event type, to check a channel set up through create_notification_settings is receiving.

Unlink, 1 operation

  • unlink_workflows_from_templateUnlink workflows from templatePOSTRemove the template association from workflows (does not change workflow config)

Version, 1 operation

  • publish_template_versionPublish template versionPOSTCreate a new immutable version of a template with prompt, schema, and/or data validation

Use Kadoa from Claude Code, Cursor or Codex

Connect Kadoa in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Kadoa operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Kadoa

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Kadoa once

    Add your Kadoa connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Kadoa integration FAQ

What can you do with the Kadoa integration?

LiveContext exposes 57 operations on Kadoa, covering schema, channel, settings and template.

Popular integrations

Browse the whole catalog