KaidayDocs
Start here
  • Overview
  • Why solo wins now
  • Getting started
  • Concepts
  • What Kai can do
Setup guides
  • Add a domain
  • Set up email
  • Connect data & tools
Platform
  • Workspaces
  • Automations
  • Control & governance
MiniApps
  • What MiniApps are
  • Templates
  • MiniApp SDK
  • Use cases by persona
Use cases
  • Common workflows

Platform

Automations

Where Kai's work happens and where you watch it. Two tabs: Tasks (individual operations) and Workflows (the pipelines that schedule them).

Tasks

★ The Tasks tab: a task running, a failure with the inline error, clicking Open conversation to jump back to the chat that produced it.

Every operation Kai runs for you shows up here as a task. Examples from a real workspace:

  • "Update the client portal". Kai edited a MiniApp for you.
  • "Add a budget field to the intake form". Kai changed code in your connected repo.
  • "The checkout isn't working". Kai diagnosed the issue from your chat.

Each task carries:

  • Status, Active, Done, Failed, or Cancelled.
  • Origin, Chat (you asked Kai for it) or Workflow (a pipeline scheduled it).
  • What Kai did (e.g. "edited the client portal", "opened a pull request", "sent the welcome email").
  • Elapsed time, the conversation link, and an expandable activity log.

When a task fails, you'll see the actual error message inline, not a generic "something went wrong." Click Open conversation to jump to the chat that produced it and ask Kai to retry or change approach.

Workflows

Workflows are the recurring or event-triggered pipelines that produce tasks. Examples:

  • New form submission in MiniApp → create a Business contact, send a welcome email, book a Calendar slot.
  • Email matches support pattern → create a Planning item, draft a reply.
  • Every Monday at 7am → digest yesterday's social mentions into Messaging.

Build a workflow either visually in the Workflows tab, or just ask Kai: "when a new lead fills the intake form, send me a DM and book them on my calendar." Kai turns the sentence into a workflow, shows you the steps, and runs it.

Work Rules (in Planning)

A separate mechanism, deliberately not bundled with Automations. Work Rules act only on planning state.

  • Items inactive 7 days move to Review.
  • Goals missing an owner for 24 hours notify the admin.
  • Work items tagged customer always get a reviewer assigned.

Configure them in Planning → Work Rules.

Two systems, on purpose
Mixing automations with planning policies creates rules that are hard to reason about. "When a payment arrives, mark the goal complete" has two parts: a Workflow (event → action) and a Work Rule (planning state policy). Keeping them separate keeps each system small and the task log readable.
WorkspacesControl & governance