Record real actions
Capture clicks, text entry, Enter, and navigation as you work on HTTP(S) pages.
Private by design. Powerful by default.
Turn browser work into repeatable flows.
Record actions, build nested loops, and extract structured data—all while keeping your workflows and results local in Chrome.
No account required No cloud processing No tracking
Built for real browser work
More than a macro recorder.
Turn complex, repeated tasks into clear, editable flows without moving your workflow data to somebody else’s server.
Build loops inside loops
Process matching rows, repeat action groups, and nest or sequence loops with explicit limits.
Extract structured data
Name the fields you need and merge multiple extraction steps into clean local records.
Handle dynamic pages
Use waits, bounded retries, conditions, pagination, and target recovery for changing interfaces.
Edit with confidence
Use the visual workspace, outline, undo and redo, target repair, step tests, and preflight checks.
Export when you choose
Keep the latest result set in Chrome, then download CSV or JSON only when you ask.
How it works
From task to reusable flow.
Start with what you already know how to do: the work itself.
- 01
Record it live
Start on the exact page, then click and type normally. Choose extraction targets without activating them.
- 02
Shape the flow
Review the tree, group steps into loops, add conditions or waits, set limits, and run preflight checks.
- 03
Run and export
Acknowledge the safety notice, follow progress, stop at any time, and export local results when you choose.
A workspace for the whole flow
See the structure.
Stay in control.
Build and inspect recursive workflows on a visual canvas with a synchronized outline. Stable node identities keep editing, diagnostics, and run history connected.
- Nested and sequential loop containers
- Target repair and individual step testing
- Undo, redo, preflight, and run diagnostics
Local by architecture
Your workflow data stays in Chrome.
gukul does not operate a developer server. Saved workflows, selected page content, extracted results, and run history stay in Chrome storage on your device.
01No analytics or advertisingNo tracking pixels, ad networks, or behavioral profiles.
02Passwords are never recordedSensitive run inputs have no saved default and are session-only.
03You decide when data leavesOnly explicit download or copy actions create output you control.
Power with guardrails
Automation can act for you.
gukul makes that clear.
Recorded clicks and inputs can have real, irreversible effects. gukul does not pretend dynamic pages are risk-free—it gives you explicit checks and visible outcomes.
Live recording warning
Recording acts on the page except while selecting rows or extraction targets.
Required acknowledgement
Execution asks you to acknowledge that automated actions can make permanent changes.
Stop stays available
Stop from the page toolbar, popup or workspace, or press Escape.
No guessing
Ambiguous, covered, disabled, or missing later targets stop with an understandable outcome.
Questions, answered
Frequently asked questions.
Where does gukul store my data?
Saved workflows, settings, latest extraction results, and bounded run history remain in Chrome storage on your device. Sensitive run inputs use session storage and are removed when the run session ends.
Does gukul send analytics or use cookies?
No. The extension does not send analytics, and this website ships without analytics, advertising scripts, accounts, or cookies by default.
Can a recorded workflow make permanent changes?
Yes. Recording is live, and replayed clicks or text entry can change or delete data on a page. gukul shows safety acknowledgement and preflight information, but you should review every flow before running it.
What can I extract?
You can select rendered text or a form control’s value, give each field a unique name, and export the resulting records as CSV or JSON.
Which pages are supported?
gukul works on HTTP(S) pages. Cross-origin iframe target selection, file inputs, passwords, arbitrary keyboard shortcuts, rich-text formatting, and automatic activation of unrecorded pagination controls are not supported.
Do workflows run in the cloud?
No. gukul runs locally in Chrome. Workflow definitions and extracted data stay there unless you explicitly export, copy, or back them up.
Less repetition. More control.
Make browser work repeatable.
Record once, shape the flow, and replay it locally with clear safety checks.
Get gukul for Chrome Available now on the Chrome Web Store.