Book a demo Sign up

Agentic workflows, governed from the first node.

Compose agents, skills, tools and human approvals on one canvas. Test them with evaluations, ship with permissions and audit already on, and watch every run.

Vendor contract reviewRun 4,218 · paused
New contract
Intake
Legal Review Agent
Redline against playbook
Fact check
Score 0.93
Counsel approval
Waiting on Priya M.
E-signature
DocuSign
6.4s
Agent time
$0.24
Cost so far
3 of 5
Steps done
50+
role-based agents to start from
50+
native, permission-aware connectors
Any node
can pause for a human decision
Every run
traced, scored and replayable
The canvas

Agents, skills, tools and people, wired together.

Drag the pieces of a process into one flow. Each step has an owner, permissions, a spend limit and a record of what it did. Click a node to see how it is set up.

Vendor contract reviewv14DraftStagingProductionLive Test run
HighLow
+ Add nodeFit view
Trigger
New contract
Configuration
Starts fromShared inbox or intake form
Also supportsSchedule, webhook, Kroolo event
PayloadAttachment plus sender
DedupeSame file ignored for 24h
Governance
Who can editLegal Ops
Data classConfidential
Retention90 days of run data
Last 30 days
212
Runs
99.6%
Started clean
0
Policy blocks
Agent
Legal Review Agent
Configuration
ModelFrontier model, routed
SkillsClause extraction, Redline
ToolsKroolo Search, Contract library
MemoryThis run only
Governance
Reads asThe requester, not an admin
WritesComments in a draft only
Spend cap$0.40 per run
Last 30 days
4.1s
Median time
$0.18
Cost per run
96%
Tool accuracy
Agent
Risk Agent
Configuration
ModelFast model for scoring
SkillsRisk scoring, Precedent lookup
ToolsKroolo Search, Salesforce read
OutputScore 0 to 100 with reasons
Governance
Reads asThe requester
WritesNothing outside this run
Spend cap$0.15 per run
Last 30 days
2.3s
Median time
$0.06
Cost per run
97%
Agrees with reviewers
Evaluation
Fact check
Configuration
CheckEvery claim cites a source clause
ScorersRules plus a model judge
Pass mark0.90 or higher
If it failsRoute to review, never to send
Governance
Who can editWorkflow owners
Change needsApproval from AI governance
LoggedScore and evidence per run
Last 30 days
94%
Pass rate
0.93
Average score
6%
Sent to review
Branch
Risk score
Configuration
RuleScore above 70
HighGoes to counsel for approval
LowGoes straight to signature
FallbackCounsel if no score
Governance
Rule changesVersioned and reviewed
AuditBranch taken is logged
OverrideNot allowed at runtime
Last 30 days
18%
Take high path
82%
Take low path
0
Fallbacks used
Approval
Counsel review
Configuration
ApproverLegal counsel group
WhereKroolo chat, email or Slack
ShowsDraft, risks, evidence
Timeout24h, then escalate
Governance
SeparationRequester cannot approve
DecisionSigned and time stamped
ReasonRequired when rejected
Last 30 days
2.4h
Median wait
91%
Approved as is
0
Timeouts
Action
E-signature
Configuration
ConnectorDocuSign
ActionCreate envelope and send
Runs asService identity, scoped
IdempotentSafe to retry
Governance
Allowed toolsAllow list per workflow
Needs approvalAlways, for send actions
AuditRequest and response stored
Last 30 days
194
Sent
0
Duplicates
1
Retried

Example workflow with illustrative figures.

Building blocks

Multiple nodes. One mental model.

Everything a real business process needs, on the same canvas, with the same controls on every piece.

Triggers
Start from an email, form, schedule, webhook or any event in Kroolo Work, CRM or Search.
What changed in my pipeline today?
Kroolo AI
2 deals moved to Proposal; 1 slipped a week.
Agents
Drop in one of 50+ role agents or your own, each with its own model, memory and limits.
Review Q3 launch planDone
Sign off budgetIn review
Brief the design teamTo do
Skills
Reusable know-how an agent can call, such as redline against a playbook or reconcile an invoice.
NameValue
Quote #1042$8,400Sent
Quote #1043$21,900Approved
Quote #1044$5,150Draft
Tool actions
Read and write across 50+ connectors, as the person who started the run or a scoped service identity.
Connected sources5 live
Synced 2 min ago
Logic
Branch, loop, run in parallel, wait, retry and handle errors without writing code.
NameValue
Acme IndustriesAnn HoActive
Paragon LabsClive BakerReview
Pioneer DynamicsKate WilsonActive
Human approval
Pause for a decision in chat, email or Slack, with the draft and evidence in front of the approver.
Draft PRD for feature XDone
Assign new bugs to triageDone
Weekly status digestRunning
Evaluations
Score output with rules and model judges, then block, retry or route to review.
Pipeline created, by monthThis year
Aug
Sep
Oct
Nov
Knowledge
Ground steps in permission-aware search over your documents, tickets and data.
Access, enforced at retrieval
Finance teamRead
Sales leadsRead, edit
ContractorsNo access
Multi-agent

Agents that work as a team, not a pile of bots.

Choose how agents cooperate. Kroolo handles the handoffs, the shared context and the limits, so a team of agents stays predictable.

Intake
Review
File and notify
Sequential

Hand work from one agent to the next, with context carried across.

  • Each agent keeps its own permissions
  • Context passes as a structured brief
  • Stop or branch between any two steps
Best for: Intake to review to filing
Contract in
Legal
Finance
Security
Merge findings
Parallel

Fan work out to specialists at once, then merge the findings.

  • Run legal, finance and security together
  • Merge with a rule or a lead agent
  • One slow branch cannot hide a failure
Best for: Faster reviews with more coverage
Orchestrator
Sales
Product
Data
Shared memory
Orchestrated

A lead agent plans, delegates and checks, using shared memory.

  • Lead agent splits the goal into tasks
  • Specialists report back with evidence
  • Hard limits on depth, spend and time
Best for: Open-ended goals with guardrails
Skills and tools

Give agents the skills, then only the access they need.

Skills package how your best people do a job. Tool actions connect that skill to real systems, with read, write and approval rules set per workflow.

  • Skills are versioned, owned and reusable across agents
  • Agents act as the requester, so permissions carry through
  • Write actions can require approval every time
  • Bring your own tools with MCP or an API call
Skill · Redline against playbookv6
InputsContract file, counterparty, region
StepsFind clauses, compare to playbook, draft edits
Tools usedKroolo Search, Contract library
Examples12 approved redlines
OwnerLegal Ops
Used by3 workflows, 5 agents
Tool access in this workflow
Salesforce
Read
HubSpot
Read
Jira
Read and write
SharePoint
Read
Databricks
Read
Slack
Write
Microsoft Teams
Write
Zendesk
Read and write
ServiceNow
Needs approval
Governance and audit

Control that ships with every workflow.

Governance is not a later project. It is part of each node, so risk and compliance teams can say yes sooner.

Permissions per node
Every agent and tool runs as a named identity with the least access it needs.
Access, enforced at retrieval
Finance teamRead
Sales leadsRead, edit
ContractorsNo access
Approval gates
Require a person for spend, send, delete or any step you mark sensitive.
Review Q3 launch planDone
Sign off budgetIn review
Brief the design teamTo do
Policy guardrails
Block PII leaks, limit spend, restrict tools and keep data in region.
GR1Auth context enforcedCritical
GR2Source citation requiredHigh
GR3PII masked in outputMedium
Versions and environments
Draft, stage and promote with review. Roll back in one click.
Funnel, last quarter
Leads1,240
Qualified570
Proposal298
Won94
Immutable audit trail
Who changed what, what each agent did and why. Export to your SIEM.
Access, enforced at retrieval
Finance teamRead
Sales leadsRead, edit
ContractorsNo access
Access reviews
See which agents can reach which systems and retire what is unused.
Access, enforced at retrieval
Finance teamRead
Sales leadsRead, edit
ContractorsNo access
Audit logExport
10:42:07Priya M.Approved send · Counsel reviewAllowed
10:41:12Legal Review AgentRead 14 clauses · Legal ReviewAllowed
10:41:03Risk AgentRead account record · Risk AgentAllowed
10:40:58Policy engineBlocked external email · E-signatureBlocked
09:12:30Dana K.Published v14 · WorkflowReviewed
09:05:44Dana K.Raised spend cap · Risk AgentPending

Illustrative entries.

Evaluations

Test agents before they touch real work.

Turn real runs into test sets, score every change against the last version, and stop a regression before it reaches production.

  • Build datasets from past runs, with sensitive fields masked
  • Score with rules, model judges and human review
  • Compare versions side by side on quality, cost and speed
  • Gate publishing on the scores you choose
  • Keep scoring live runs to catch drift
Evaluation · Contract reviewPassed gate
120 test cases3 scorersCompared with v13
Groundednessv13 92% → v14 94%
Policy adherencev13 97% → v14 98%
Tool accuracyv13 95% → v14 96%
Reviewer agreementv13 90% → v14 93%
Release gate: block publish if groundedness drops below 90%.

Illustrative results.

Run 4,218 · trace Replay
New contract0.1s—
Legal Review Agent4.1s$0.18
Risk Agent2.3s$0.06
Fact check0.8s$0.01
Branch · risk 820.1s—
Counsel review2.4h—
E-signature0.6s$0.00
7
Steps
$0.26
Total cost
3
Policy checks

Illustrative run.

Observability

See every run, step by step.

Open any run to see which agent did what, with which tool, at what cost, and why a branch was taken. Replay it with a new version before you ship.

  • Full trace of prompts, tool calls and decisions
  • Cost and latency by step, agent and team
  • Alerts on failures, drift and spend
  • Retry or resume from any step
Lifecycle

From first draft to governed production.

One path for every workflow, so the tenth one is as safe as the first.

01
Build
Compose nodes on the canvas or describe the process and let Kroolo draft it.
02
Test
Run test cases and compare with the last version.
03
Govern
Set access, approvals, limits and policies.
04
Ship
Promote through staging to production, with rollback.
05
Monitor
Trace runs, track cost and score live output.
Templates

Start from a working process.

Each template wires up agents, skills, approvals and evaluations. Edit it to match how your team really works.

Contract review
7 steps
Redline, score risk, route to counsel, send for signature.
Use this template
GR1Auth context enforcedCritical
GR2Source citation requiredHigh
GR3PII masked in outputMedium
Month-end close
9 steps
Reconcile, explain variances, route exceptions to the controller.
Use this template
Draft PRD for feature XDone
Assign new bugs to triageDone
Weekly status digestRunning
Incident triage
6 steps
Classify, find owners, draft updates, open and track the ticket.
Use this template
Open deals
128
+12
Avg. cycle
47 d
-3 d
Candidate screening
6 steps
Screen against the role, schedule, summarise for the panel.
Use this template
Access, enforced at retrieval
Finance teamRead
Sales leadsRead, edit
ContractorsNo access
Vendor onboarding
8 steps
Check documents, assess risk, create the vendor in ERP.
Use this template
GR1Auth context enforcedCritical
GR2Source citation requiredHigh
GR3PII masked in outputMedium
Renewal risk
5 steps
Spot at-risk accounts, draft outreach, alert the owner.
Use this template
GR1Auth context enforcedCritical
GR2Source citation requiredHigh
GR3PII masked in outputMedium
Why Kroolo

Automation, agents and governance, finally in one place.

Most teams stitch together a flow tool, an agent framework and a compliance review. Kroolo gives business and IT one surface.

Classic automationAgent frameworksKroolo AI Workflows
Visual canvas for business ownersYesMostly codeYes
Multi-agent orchestrationLimitedYesYes
Permission-aware access to company dataPer connectionYou build itBuilt in
Human approval on any stepSomeYou build itBuilt in
Evaluations and release gatesRareAdd-on toolsBuilt in
Audit trail and versioningBasicYou build itBuilt in
Cost and spend limits per runRareYou build itBuilt in

Typical capabilities by category, not a comparison of any single product.

FAQs on AI Workflows

Can business teams build these, or only engineers?
Both. Business owners can compose and test on the canvas or describe a process in plain language. Engineers can add code, custom tools and MCP servers to the same workflow.
How do agents get access to our data?
Agents act as the person who started the run, or a scoped service identity you approve. Retrieval respects the permissions of the source system, so people and agents only see what they are allowed to.
What happens when an agent is wrong?
Evaluation gates and approval steps catch problems before anything is sent or written. Every run is traced, so you can see why it happened, replay it and fix the version.
Which models do workflows use?
Kroolo uses leading models from Anthropic, OpenAI and Google. AI Inference routes each step to the model that fits the job and keeps spend within limits.
Can we keep workflows out of production until they are reviewed?
Yes. Workflows move from draft to staging to production, with required reviewers, evaluation gates and one-click rollback.
Does it work with our existing tools?
Kroolo connects to 50+ tools, including Slack, Microsoft 365, Google Workspace, Salesforce, Jira, SAP and Snowflake. See the Connectors page for the full list.

Bring a real process. See it run, governed.

We will build it on the canvas with you, run the evaluations and show the audit trail.