# Kadoa integrations: workflows and workflow data

> Create a workflow, create a data export and create a schema in Kadoa, and start a workflow when Kadoa sends “Workflow data changed”.

**Canonical page:** https://tray.ai/connectors/kadoa-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Kadoa is an AI web scraping platform that runs scheduled workflows to pull structured data from websites and flag changes. Tray.ai connects to Kadoa through the HTTP Connector, so your workflows can call the Kadoa API alongside the rest of your stack.

## Use cases

### Workflows

Read, create, and delete workflows in Kadoa from any Tray.ai workflow. The Kadoa API covers calls such as list workflows and create a workflow.

- List workflows
- Create a workflow
- Run a workflow

### Workflow data

Read and create workflow data in Kadoa from any Tray.ai workflow. The Kadoa API covers calls such as get workflow data and create a data export.

- Get workflow data
- Create a data export
- Download a data export

### Data changes

Read data changes in Kadoa from any Tray.ai workflow. The Kadoa API covers calls such as list data changes and get a data change.

- List data changes
- Get a data change

### Schemas

Read, create, update, and delete schemas in Kadoa from any Tray.ai workflow. The Kadoa API covers calls such as list schemas and create a schema.

- List schemas
- Create a schema
- Update a schema

### Notification channels

Read, create, update, and delete notification channels in Kadoa from any Tray.ai workflow. The Kadoa API covers calls such as list notification channels and create a notification channel.

- List notification channels
- Create a notification channel
- Update a notification channel

### Kadoa events

Start a Tray.ai workflow the moment something happens in Kadoa. Kadoa sends events such as workflow data changed and workflow finished to a Tray.ai webhook trigger.

- Workflow data changed
- Workflow finished
- Workflow failed

## Challenges Tray.ai solves

### Keeping Kadoa credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Kadoa credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Kadoa API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Kadoa API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Kadoa?

Yes. Tray.ai connects to Kadoa through the HTTP Connector, which calls the Kadoa API directly. Any call the Kadoa API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Kadoa?

The Kadoa API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Kadoa connector?

Kadoa runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Kadoa connector from the Kadoa API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/