Searchable documentation with focused articles, examples, step-by-step guidance, copyable snippets, and related feature links.
Install Advflow, choose local or cloud storage, and create a workflow that opens your project tools.
Open Advflow and choose local storage for private desktop-only workflows.
Create a workflow from the Workflows page.
Add openApp, runCommand, and openBrowser nodes.
Run once, review the result, then save it as a reusable setup.
Workflows are ordered node collections that run local desktop automation steps in a predictable sequence.
Name the workflow around the outcome, not the tool.
Keep commands scoped to a working directory.
Use delay nodes only when an app or server needs startup time.
Export workflows when sharing with teammates or community posts.
{
"type": "runCommand",
"command": "npm run dev",
"workingDirectory": "C:/Projects/app",
"shellType": "powershell",
"terminalType": "background"
}Macros cover direct desktop gestures such as key presses, mouse clicks, text entry, and deliberate waits.
Use hotkey nodes for repeatable shortcuts.
Use typeText only for trusted local text.
Keep mouse coordinates reserved for stable desktop layouts.
Wrap fragile sequences with short delay nodes.
[
{ "type": "hotkey", "keys": ["ctrl", "shift", "p"] },
{ "type": "typeText", "text": "Developer: Reload Window" },
{ "type": "pressKey", "key": "enter" }
]Command nodes run through your selected shell and should define a timeout, directory, and terminal behavior.
Prefer background commands for short checks and new terminals for long-running servers.
Set commandTimeoutSeconds in Settings to avoid stuck runs.
Use PowerShell or cmd on Windows depending on your script needs.
Review stderr when a command node fails.
runCommand({
command: "cargo check",
workingDirectory: "C:/Users/you/project/src-tauri",
shellType: "powershell",
terminalType: "background"
})Advflow can connect desktop apps, shells, browser routes, MongoDB storage, Gemini, and local model endpoints.
Pick preferred editor and browser in Settings.
Add Gemini or local model credentials only when using AI generation.
Use MongoDB storage when workflows need sync across machines.
Export shared workflows before posting them in Community.
Settings control local/cloud storage, command timeouts, compact UI, destructive confirmations, and startup behavior.
Keep confirmDestructiveActions enabled for shared libraries.
Tune commandTimeoutSeconds for your slowest safe command.
Use syncOnOpen only with a known-good MongoDB connection.
Enable developer mode while testing workflows and community exports.