Browzer
Build any automation with a click - the n8n alternative
108 followers
Build any automation with a click - the n8n alternative
108 followers
Browzer is an AI-powered workflow automation tool that learns your repetitive tasks and processes to automate them with 1 prompt. Record once & automate forever. Browzer doesn't assume your processes like other agentic tools & browsers, but instead understands your processes to automate work, the way you'd do it.
My Backstory that led me to build Browzer
I've worked on 3 startups in the past, sold 2 and have worked multiple jobs. I built coding agents and headless browsers in 2018, long before it was really ever a thing. I've built automation systems for over 8 years now. In my previous jobs, I built automation systems for various companies to automate non-technical tasks like HR onboarding, data collection, marketing automation, QA & testing and accounting automation, among others. While the end goals were the same, the processes that each company followed was different. But the problem is that there's 0-context about your processes. So how do you build a generic automation system? This simple question led me down the path of Browzer!
Why, What & How?
Agents today "assume" your processes. If you asked them to onboard a new employee, it wouldn't know which HR tool you use, what your process looks like or even the variables involved in making that happen. And that's where Browzer comes in!
Browzer allows knowledge workers to build any automation with a single click, by showing how you do your task once. We have inbuilt AI agents that learn how you work, and do the work the way you'd do it inside our own native browser. Record your workflows once and show Browzer how you do a particular task. Thereafter Browzer uses that as context to automate future similar workflows. Our recording feature offers everyone a frictionless way to automate any task of their choice, contrary to most other agentic workflow builders that have drag & drop mechanisms & a big learning curve, or even other agentic tools which don't usually have such a provision.
Difference between Browzer & other agentic workflow tools & browsers
Other agentic tools & browsers - you need to elaborate your process which is tiresome.
Even after this, there's going to be a ton of back & forth with the details you want the agent to enter. Instead of doing all of this, you might as well just do the task yourself.
n8n & other agent builders - Big learning curve, need to be fairly technical, loads of time to setup, build and manage. Not very user friendly unless people are plugged into this most of the time.
This is where Browzer comes into the picture - Record your EOR workflow the first time you do it, and from there on out, just prompt your in-built Browzer Assistant
Browzer understands what variables you need to enter so you can enter them before hand. This saves time, efforts and makes your life easier.
Browzer's core focus on privacy
Browzer offers a completely private automation experience - your prompts or responses are not stored. And all your data like history, workflow recordings, etc. are all stored locally on your machine.
Today, we have 30+ paying customers - which includes individuals and businesses combined. If you'd like to try Browzer out, use the code 1FREEMONTH during checkout and get 1 month of free usage for Browzer's Pro & Business plans!
Common use cases with Browzer - HR Automations, UI Testing, Release Management, Crafting Emails, Managing Product Boards, Alternative to Terraform (surprising but it's true)!
Do give us a try by Downloading Browzer from here - https://trybrowzer.com/download. I'd love to hear your feedback, both positive and negative. Our goal is to make as delightful a product as possible for you and that's possible only when we hear from you! If you'd like to reach me via email, drop me an email - rahul[at]trybrowzer[dot]com
Congrats on the launch! The show it once, then automate approach feels like a strong answer to the context gap most agents struggle with. How does Browzer generalize a recorded workflow into reusable logic, especially when the same task changes slightly over time or involves edge cases that weren’t present in the original recording?
@vik_sh Thank you, Viktok and great question.
So whenever we record a workflow, we first templatize it to understand all the variables associated with your workflow. Templatizing the workflow allows us to use it as a plug and play system if it is a truly repetitive task. However, we do understand that sometimes there could be variations of a workflow. For example - let's assume a user records a workflow on Browzer to create a private repository on GitHub. Now, the workflow recorded shows how to create a private repo but because of how we templatize things we are able to also run the same recording to create a public repo if needed.
Coming to your part about same tasks changing slightly over time - yes, that's very much a possibility. But let's say if a task changes slightly, it is always recommended to create a new recording. However, even if you don't, you'd be able to prompt Browzer Assistant to do the task with the constraints/changes you have and it would do the task with your changes/constraints.
Taking that a step forward - sometimes websites itself change, new UI, new components and this would break traditional automation systems. But Browzer adapts! Our unique AI first approach maps your existing recording to the new UI that exists and gets things done for you.
In case of edge cases that Browzer's not sure about, we will be adding a feature where Browzer would ask you clarifying questions before acting.
@shubh99 - in an ideal world, you should be able to automate anything. If you can access a website on Browzer, you can automate it (and most websites do work on Browzer). Some websites (for example - WhatsApp Web), block Browzer from accessing their website (because we're built in electron). But 99.99% of the websites are accessible through Browzer and if you can open it on browzer, you can create a workflow to automate things on that website.
About your linkedin example - yes, that should ideally work. However, we do have a hard limit currently on the number of steps/api requests that a single automation request can make (150 steps/20 api calls) whichever comes sooner. We don't look at workflow duration, but limit based on steps/api calls. Long horizon tasks will soon be supported in Browzer though (hope this answers your question about the duration aspect).
One real example from our own team: we use Browzer to automate our weekly release process.
We recorded the release checklist once, and now Browzer runs it end-to-end - checking whether all release PRs are approved, validating the checklist steps, and only then moving the release forward. No manual back-and-forth, no missed steps.
What’s nice is that it follows our exact release process.
@aditya_browzer thanks for sharing that Aditya! Yeah, recording our release workflows ensure that we don’t miss out anything during every release cycle. Plus it saves us time 🙌 thanks for sharing how we use Browzer internally as well!
The Browzer is unique from other computer agents in the way that it's Deterministic unlike other general agents. It learns how you do your task, and then automates following the path that you want. And that makes it reliable for the real world critical use cases, where determinism is the most important factor in any automation.
@abhinandan_browzer precisely. Thanks for adding that context about exactly how we're all thinking about deterministic workflows in our team! This is something that's extremely important for a variety of use cases. You need your processes to be deterministic and that's exactly what we provide. Reliable automation with robust guardrails and determinism.
LIAM
Looks dope. Will it work for bookkeeping automation, but in German language?
@sintem Thanks, Isa. We currently don't have bookkeeping automation. Curious though - what kind of bookkeeping automation are you looking for? Could you give an example/use case for it.
LIAM
@rahulkumaran313 In Germany, at the end of every quartile, I must go through each invoice PDFs and upload it to my bookkeeping system and sometimes clicks same buttons. They processes are not always the same so require some level of intelligence from the system.
Nice concept, record it once and let the agent figure out the rest. Feels way easier than setting up rigid automations. 👍
@relacosm that's the goal! Because it makes no sense to spend days building rigid automations, only for them to eventually break. AI + determinism + process-awareness is what's needed for businesses to adopt automation tools at scale.