Enterprise workflows
Workflows for every department, each done end to end
Each workflow takes one job from trigger to finished result, with an AI agent working in a real browser in the tools your team uses.
A worklist that keeps its place
Workflows that work through a list keep a persistent worklist of what is done, next and skipped, so each run picks up where it stopped.
Sample Static worklist: contact 40 wedding florists from a lead list, every 15 minutes. 14 of 40 handled, including 1 skipped, and 25 up next. Working on item 15, Petal & Stem Co.
Sample Dynamic worklist: check competitor prices on 8 product pages, daily at 07:00. Cycle 14: 6 of 8 checked, 2 changes found and 4 unchanged.
Sample Monitor worklist: act on every update to our open orders, every 5 minutes. One order is under Needs you: 3 updates handled and 2 waiting, which clear on the next run.
Static
Walked top to bottom once.
Each item is handled one time and every skip is logged with the reason. The workflow pauses itself at the end.
Dynamic
Re-walks from the top each cycle.
Every item is checked again each cycle, so nothing goes stale, and each change gets its own log line.
Monitor
Re-checks each source on every run.
Each new item is handled once: an order update, a support ticket, a form submission or an applicant.
Know what happened to every lead
Give a workflow 40 wedding florists to contact. Here is what it tells you.
Who it contacted, and when
Each run starts at the next florist. No one is contacted twice.
What is done, and what is left
Check progress on the whole list at any time.
Why a lead was skipped
If a florist’s site is offline, it notes the reason so you can follow up.
What a workflow can do
A workflow signs in to your tools, does the work in each app and tells you how it went.
- Runs on your schedule
- Stays signed in to your tools
- Writes emails in Gmail
- Picks up where it stopped
- A policy can pause for approval
- Reports to Slack, Telegram or WhatsApp
- Records every run
- Posts screenshots to Slack
- Fills in contact forms
- Updates orders in Shopify
- A policy can block an action
- Changes when you ask
- Runs on demand
See what each workflow saves
Every workflow’s overview puts what it cost beside the same work done by hand.
Works in the tools your teams already use
WebRun signs in and works in a real browser, the way a person would, so no tool needs an API or a connector.
7,000+apps
14,000+templates
Customers and communication
Industry systems
Not on the list? Search the app guides or browse the templates.
You stay in control of every run
WebRun does not train AI models on your data or sell personal information.
Approve before it acts
A policy can block an action or pause the run until you approve it.
Replay every run
Every run is recorded, so you can replay each step.
Logins stay encrypted
Saved logins are encrypted and kept out of logs.
Workflow questions, answered
What is a WebRun workflow?
A workflow is one job for one team, written as a plain-language plan that WebRun runs end to end on a schedule or a trigger. Every Monday, for example, it finds overdue invoices in QuickBooks, drafts reminder emails in Gmail and sends you the chase list in Slack. An AI agent does each step in a real browser, signed in to your tools.
Will a WebRun workflow contact the same lead twice?
No, not in a Static worklist, which works through a list top to bottom once. Each lead is handled once and stays handled, and the worklist records what was done to every lead, so each run starts at the next one. A lead whose website is offline, for example, is skipped and logged with the reason.
What happens when a workflow reaches the end of its list?
A Static list pauses itself when it reaches the end. A Dynamic list starts again from the top each cycle, so every item is checked again and nothing goes stale. A Monitor list has no end: it re-checks each source on every run and handles each new item once. You choose the mode for each workflow.
What happens if a workflow cannot finish an item?
If an item cannot be done, for example because a lead’s website is offline, it is skipped, logged with the reason and counted on the worklist, and the workflow moves on to the next item. An item that only needs more time continues in the next agent session, which costs another cent.
How do I approve what a workflow sends, posts or pays?
Attach a policy to the workflow. A policy can block an action, or pause the run before anything irreversible, such as sending email, posting or spending, so you can approve it, reject it or take over. Without a policy, the agent follows the workflow’s plan unscoped. Policies are checked before every action, at the infrastructure level rather than in the prompt.
Which tools does WebRun work with?
WebRun works in the tools your team already uses by signing in and using them in a real browser, the way a person would. No API wiring or connector is needed. The template library covers 7,000+ apps, from Slack, Gmail and Google Sheets to Salesforce, NetSuite and ServiceTitan, with 14,000+ ready-made workflows.
How much does a workflow cost to run?
About 1 cent per task, where a task is one job done end to end. Tasks come from your plan: Starter is $20 a month for about 2,000, with a 7-day free trial and no credit card. Pro is $100 for about 10,000, and Business is $200 for about 20,000. There is no per-seat pricing and no setup fee.
Give every team workflows that finish the job
Start free with a 7-day trial on Starter and no credit card, or book a demo to plan workflows for every department.