Skip to main content
Step-by-step tasks for Kadoa’s agent in the dashboard, from code, and over MCP. For what the agent does and how its two chats differ, see Agent.

Before you begin

  • The agent works in the dashboard, the Node SDK, the REST API, and the Kadoa MCP server. It is not available in the Python SDK yet.
  • The SDK namespace (client.assistant), the API paths, and the MCP tool names say assistant. They control the same agent.
  • Agent requests from code are asynchronous. Save the returned workflow, session, and thread IDs. Use them to check the agent’s current state or a pending question.

Open the agent

In the dashboard:
  1. Select Agent in the bottom-right corner of any page.
  2. Select This workflow to work on the workflow you have open, or Workspace for everything else. See Two chats.

Change or fix a workflow

Send the agent a change request instead of deleting and recreating the workflow. The workflow keeps its ID. The agent investigates, makes the change, and reruns a sample so you can confirm the fix before anything goes live.
  1. Open the workflow and select Agent.
  2. Describe what is wrong and what you expected, for example “The salary field is empty on most rows, but the postings show a salary near the title.” The agent looks into the workflow and adjusts the extraction, schema, navigation, or transformation. It then reruns the preview and tells you what it changed as it works. The agent working through its plan and narrating each step
  3. Check the updated sample rows. The review state: a table of sample rows with Approve and Report problem actions, and a note that no quota is used until you approve
  4. If the sample looks right, select Approve to apply the change. If not, reply with what is still off and the agent reruns. Repeat as many times as you need.
The agent can investigate and fix issues across the whole workflow: For automatic checks on every run instead of spot-fixing, add data quality rules.

Answer the agent’s question

The agent can pause to ask for clarification. A workflow waiting on you shows Reply needed, and a dot appears on Agent. After you answer, the agent resumes.
  1. Open the workflow that shows Reply needed.
  2. Select Open agent.
  3. Pick an answer, or select Other and type your own. Some questions take free text instead.
  4. Select Submit.

Create a real-time monitor

Use a real-time monitor when you want continuous change detection and alerts. It is a separate workflow mode. Do not convert a scheduled workflow to real-time by changing its interval. A real-time monitor needs at least one notification channel.
  1. Select Agent. If the chat shows This workflow, select Workspace.
  2. Name the pages to watch, the changes you care about, and the channel for alerts. For example, “Monitor product prices on https://example.com/products and alert me by email when they change.”
The agent creates one monitor per website.To build a single monitor from the setup prompt instead, select Real-time as the workflow type. See Use the setup prompt.
For scheduled and one-time extractions, notifications are optional. See Notifications to configure channels and Change detection for how Kadoa identifies changes.

Pause or stop agent work

Interrupting or stopping the agent controls agent work only. It does not pause or resume the workflow schedule, and stopping does not delete the workflow.
  1. While the agent works, select Interrupt below the chat.
  2. To continue, send a message with new instructions or select Continue.

Read the conversation and strategy

The timeline shows customer-visible messages and clarification questions. It excludes internal and operations activity. In the dashboard, the workflow chat shows the same conversation.
Pass nextCursor from one response as cursor to read older entries.
Node SDK
When a build has produced a customer-safe strategy, you can retrieve its approach, data source, and realtime interval. A null strategy means the session exists but has not produced one yet.
Node SDK

Use Workspace chat

Workspace chat is for work that spans workflows. It is dashboard-only, and API keys cannot open it. It uses the same tools and role permissions as the Kadoa MCP server. Your AI tool can do the same work over MCP. Either way, build and repair work goes to the same agent.
  1. Select Agent. If the chat shows This workflow, select Workspace.
  2. Type your request and send it.
To start a new chat, select +. To open or delete past chats, select History.

Ask about your team’s workflows

Ask about any workflow, run, or change. Try “Which workflows failed this week?” or “Who changed the schedule on Job Postings?” A Workspace chat answering which workflows ran today and how many rows each returned

Create workflows in batch

Name several websites in one message, such as “Track job postings (title, location, salary, apply link) on acme.com/careers, globex.com/jobs, initech.com/open-roles”. The agent proposes a shared template and the website list. Confirm, or name an existing template to reuse. The agent then creates one workflow per website and reports any failures. Each workflow previews for you to approve. For real-time monitoring, the agent creates one monitor per website. This needs a notification channel.

Find sources

Describe the data, such as “Find me sources for UK planning applications”. The agent searches the web and opens pages in a browser when needed. It lists candidate URLs with what each likely carries and what it checked. A workflow run confirms the data. The agent never submits forms that change anything or enters credentials.
A Workspace chat answering a request for European fintech career pages: ten candidate URLs, each marked as company-run or job board, with what each page shows

What to say

Brief the agent like a colleague. Lead with the symptom and the result you expect. Name the field, the page, and what the correct value should look like. The same advice as writing a good prompt applies.
In a workflow chat, type $ to reference a saved variable, such as a login value. Type @ for a notification channel or # for a tag. See Use the setup prompt.
Rules you repeat on every workflow belong in AI personalization instead. The agent reads them when it starts on a new workflow.

When the agent can’t fix it

The agent tells you and automatically hands the issue to Kadoa support. For how Kadoa classifies and auto-recovers failed runs, see Error handling.