Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.klarity.ai/llms.txt

Use this file to discover all available pages before exploring further.

A process performer — an AP lead, ops manager, recruiter, analyst — asks their assistant to do real work: vendor reconciliation, invoice approval, candidate screening, ERP migration prep, audit walkthrough. The assistant should pull the customer’s existing process before improvising.

​
Example prompts

  • “Walk me through how to reconcile this batch of vendor invoices.”
  • “Help me prep for tomorrow’s SOX walkthrough.”
  • “I’m onboarding a new vendor — what’s our checklist?”

​
End-to-end recipe

1

Confirm the workspace

Call list_accessible_workspaces and switch with switch_mcp_workspace if the user names a workspace other than the active one.
2

Search for the process

Call search with the task in the user’s words (“vendor invoice reconciliation”). Iterate two to four times with refined queries — single queries rarely cover broad topics.If results are still sparse, call get_process_hierarchy_tree to orient on the right value stream, then drill in.
3

Fetch the matched process

Use fetch to read steps, policies, inputs, outputs, and dependencies. If you need the richer nested payload (full version metadata or every dependency ID), call get_process_details directly.
4

Pull recent observations

Call get_recent_process_observations and get_process_observations to find emerging edge cases and exception patterns.
5

Drill into the most relevant session

Call get_observation_activity_timeline to read the exact user actions behind a deviation. This is the most “primary source” evidence the workspace has.
6

Check boundaries (optional)

If the task touches another team or system, call get_upstream_sources or get_downstream_dependencies to map handoffs.
7

Synthesize

“Here’s how your team does this. Here’s the deviation pattern from last quarter. Here’s what to watch for.”

​
Catch duplication

If the user suspects a different team already does this work, search across teams or business units for similar processes and traverse the graph for related entities. Surface the duplicate set with process IDs.