What are HEIDI guided workflows?
HEIDI guided workflows are in-browser assistance paths for operational work: edit automations with natural language (vibe coding), capture browser and desktop evidence for task mining, execute configured workflows via the runtime, and send SOP onboarding invites so new hires learn with HEIDI.
Capabilities
What you can do with HEIDI
Vibe coding for workflows
Describe changes in plain language; HEIDI helps build or modify workflow automations in context.
Task mining capture
Record browser and desktop evidence during real work to feed HEIDI and automation design.
Controlled execution
Run workflows through the runtime API with telemetry and approval gates — not unchecked auto-runs.
SOP onboarding invites
Send SOP plus HEIDI onboarding invites so new team members learn procedures with guided assistance.
Stays in the browser
Guidance overlays operational UIs — operators do not context-switch to separate documentation.
Use cases
Where teams apply HEIDI
Real workflows that benefit from visual design, automation, and governance.
Modify a workflow by description
Tell HEIDI what should change in the automation; review the proposed edits before they go live.
Capture a process for task mining
Record clicks and navigation across tabs to build evidence for process analysis and automation.
Execute an approved workflow
Launch a configured workflow run with full observability and recovery rules.
Onboard with an SOP invite
Send a generated SOP and HEIDI invite so the hire walks through the procedure with assistance.
SOP step with exception handling
HEIDI guides the standard path and surfaces policy when an exception requires approval.
How it works
From chaos to clarity in 4 steps
Open Guided Workflows
From Assistance Hub, choose vibe coding, capture, execution, or SOP onboarding.
Work in context
HEIDI stays aware of your project and the application you are operating in.
Propose the next step
Edits, captures, or runs are prepared — not silently applied.
Review and approve
Operators confirm before workflows execute or changes are saved.
Record and improve
Telemetry and captures feed back into Operational Knowledge and future guidance.
Avoid these
Common mistakes (and how to avoid them)
Running production workflows without observability
Silent failures in operations are hard to debug and audit.
Use the runtime execution path with step telemetry and defined recovery rules.
Training new hires on PDFs alone
Static SOPs do not adapt when the UI changes or exceptions appear.
Pair SOP content with HEIDI-guided onboarding invites in the live application.
Vibe coding and task mining
Guided workflows bridge human operation and automation design without a separate tooling silo.
Vibe coding lets operators describe workflow changes in natural language while HEIDI proposes concrete edits to review.
Task mining capture records browser and desktop evidence during real work — the same capture path used across the Process Designer platform for deterministic automation input.
See Assistance Hub for the full hub and Manual Map for navigation context.