Web automation like you've never seen it before.
7-day free trial, no credit card required. 30-day trial available with a card on file.
How would you like to use webSlinger?
Introduction to webSlinger
Four Steps from Idea to Scheduled Automation
No code to write. No selectors to hunt down. No infrastructure to configure.
Want to see how webSlinger compares to Zapier, Apify, UiPath, and Octoparse? View the comparison →
Watch It Handle the Hard Stuff
Three tutorials that show the full Plan → Record → Generate → Execute flow on real websites — including bank MFA and multi-page invoice extraction.
Extracting Data from a List
Demonstrate on one city, generate a script that fetches temperatures for any list of cities. Shows how webSlinger extrapolates from a single example to an entire dataset.
Bank Login with MFA
Full bank login with multi-factor authentication, then downloading checking transactions for a configurable date range — the workflow every other tool says you have to handle manually.
Amazon Invoice Extraction
Extracts order date, invoice total, card number, and itemized descriptions and prices across three months of orders — navigating multiple pages per invoice automatically.
Why I Built webSlinger
I was developing an AI agent that could write Python code to accomplish tasks by breaking them into phases, requiring evidence of correctness at each step before moving on. When it came to web tasks, the LLM could create a plan of what to do but couldn't figure out how to do it. It would guess at selectors, and if they didn't work it would guess again — half the time guessing the same selectors as before.
I spent a day hand-feeding it HTML snippets to help it find the elements it needed to click or fill for what seemed like a simple task. Eventually it completed the task, but with a level of hand-holding that was exhausting. I came to realize that when it comes to the web, there is a big difference between knowing what to do and how to do it. What the LLM needed was actual selectors it could use and a way of associating them with actions it needed to perform.
So I set the agent aside and started working on ways to fill the gap. The most effective approach I could come up with was to demonstrate how to do a task while monitoring the elements I interacted with and creating selectors for them. I wrote a Python program called followLeader that would replicate what I did in one tab in another tab. I developed state monitors that could determine when a tab had stabilized, and a scheme to precompute sets of selectors for every interactive element on the page as soon as the validation tab was stable — so that when I clicked in the main tab I could instantly use the corresponding selectors to reproduce the action in the validation tab. I developed feature sets that translated to selectors enabling me to uniquely identify elements based on structure and content, not position.
Finally I had followLeader operating robustly with minimal latency, but I hit a wall when navigating to my bank: Playwright's listener injection was blocked by Cloudflare. Automating downloads from my bank was a priority, so I had to find a workaround. It turns out that setting up listeners via a browser extension is not detectable. So I recoded followLeader in JavaScript and it became the core of webSlinger.
Logging into my bank was a priority and I had already developed a local vault to enable my agent to retrieve credentials, so I adapted it for webSlinger and added MFA TOTP generation. I added the ability to save the selectors generated in real time as a session map — essentially a Rosetta Stone providing a translation between what to do (steps in English) and how to do it (robust selector sets). Using the saved session map, the task description, and a well-engineered prompt, webSlinger creates the automation script to accomplish the task.
I'm pleased to share webSlinger with you all.
Built With Security as a First Principle
Automation that touches credentials and private data needs to be trustworthy by design.
Zero-Knowledge Credential Storage
webSlinger's companion extension, keyCocoon, handles password and MFA entry while keeping your credentials encrypted locally except while in use. webSlinger never touches your passwords itself — they are never transmitted to any server, ours included.
Time-Bound Master Password
You control how long keyBunker stays unlocked — from 5 minutes to 24 hours. After the window closes, credentials are locked again automatically. Scheduled tasks that need credentials re-unlock only when they run.
No "New Device" Alerts — Ever
Banks, brokerages, and government portals recognize your session because it IS your session. Hardware fingerprint, TLS profile, cookies — all genuine. No suspicious login notifications, no forced re-verification, no lockouts.
Data Stays on Your Machine
Session maps and extracted data are stored locally. The server processes selectors and generates scripts — it never sees your credentials, the financial data you extract, or the content of the pages you automate.
webSlinger isn't a wrapper around an existing automation framework. It was engineered from scratch to solve the hard problems.
Ready to Automate?
Install the extension and run through the tutorial — 7-day free trial, no credit card required (or 30 days with a card on file). Lock in 1/3-off beta pricing before July if you want to subscribe.