⚡What Flows are and what they can do

A Flow is a job you draw on a canvas instead of writing in code: open a page, wait, click, type, read something, loop, branch. You then run it on any profile, and the run drives that profile's real browser — same fingerprint, same proxy, same timezone, same cookies as pressing Run on the profile.

⚡ What makes it different from a script#

• Real input. Clicks are a pointer that travels to the element, settles and presses; typing goes in at that profile's own speed, with its own typo rate. Not element.click(), not a paste.
• Elements are matched by what they are — visible text, id, label, name, role — rather than by a CSS selector. A site redesign usually does not break the Flow. You can still give an exact selector when nothing else tells two elements apart.
• It is the same session you would open by hand. Nothing about the identity changes because a Flow is driving it.

🧭 Where Flows live#

In the left sidebar, under Operate, click Flows. The library lists every Flow with its step count, when it was last changed and its status. Along the top: Run history, Schedules, Import…, API & MCP, Templates, ✨ Generate with AI and New flow.

🚦 Three ways to get your first Flow#

Templates never need an AI model. Generate with AI does — see LoginDeck AI actions.

🧰 What a Flow can do#

There are 41 step types, in five groups:

• Flow — order, waiting, loops, branching on a condition, a percentage chance, variables, a bit of JavaScript, running another Flow inside this one.
• Browser — open a URL, tabs, back and forward, reload, wait for a page or an element, screenshot, and "browse like a person" (the warm-up robot as a step).
• Interaction — click, hover, human typing, a key press, human scrolling, choosing from a dropdown, handing a file to an upload field.
• Data — read text or an attribute off the page, an HTTP request, clipboard, the time, a random number, a list from lines or a CSV, save results to a file, and a short piece of AI-written text.
• Profile — what this identity is, and where it actually exits.

Every step type is listed with its settings in the Flow steps reference.

▶️ Running one#

Open a Flow, pick a profile in the toolbar, press ▶ Run. One profile at a time, or Run on many… for a whole list — up to 20 browsers at once. See Run a Flow on one profile or many, and Run Flows on a schedule for unattended runs.

Flows can also be started from outside the app — by your own script, or by an AI agent: Get started with the local API and Let AI agents drive LoginDeck (MCP).

🧯 What Flows will not do#

• Firefox profiles cannot be automated yet. Flows, warm-up and Synchronized Actions all need a Chromium profile. See Chrome or Firefox.
• A profile you already opened by hand cannot be taken over. Close that window first, then run the Flow.
• No CAPTCHA, phone or ID solving. Nothing in LoginDeck works around a human check.
• A Flow's JavaScript stays in the web page. Code, If / Else and expression variables run in the page, like the devtools console — they cannot reach your files or your profiles. Writing to a file is a separate step (Save to file) whose path is visible on the step, so a Flow somebody sent you cannot hide where it writes.
• A run does not survive the app closing. Runs live in memory; quitting LoginDeck ends them.

ℹ️ Good to know#

• Flows sync to your other computers and to your team, encrypted, like profiles. Run history, Schedules and your AI settings stay on the computer they were made on. See What syncs.
• One run per profile at a time. A second run on the same profile is refused with "{flow}" is already running on this profile.
• A run stops itself after 40,000 steps, which is how you find out a loop has no way out.
• Screenshots and files a run saved go into that run's own folder, and the run log tells you the path.
• Saved logins on a profile can be filled in by a Flow without you putting a password in a step: see Saved logins and 2FA codes.