Browserhub Strawberry

The Browserhub automations nobody wants to work through

Hand a companion the outcome. It reads the Browserhub automations, does the 1-operation version of the job, and stops for your click on anything that changes a record.

Open the automation. Check it against something else. Write the change. Move to the next one. That is the Browserhub afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a automation until you approve it.

What it can do is exactly what Browserhub exposes to an account you authorise and nothing beyond it: 1 operation, no reads and 1 write. In practice that means it can run an automation.

The Browserhub API stops at Browserhub. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

Does it read the automations or ask you for them?

In the tab.

Browserhub exposes no read operation to a connected account, so a companion opens Browserhub in the session you are already signed into and reads the screens you would.

The automations are what most of this inventory is about, alongside the automations. A companion can hold that operation and forty open tabs in the same pass, which is how an afternoon of Browserhub admin becomes a queue you review.

What happens before it can run automation?

The one write operation there is waits for you.

A companion can run an automation, and each one is staged on an approval card first: you see the automation, the field and the new value before it lands in Browserhub.

Nothing in Browserhub is sent, changed or deleted on your behalf without that click, and a rejected card leaves the automation exactly as it was. The gate is the same one on every surface, described at security.

  • Run Automation

What does the recurring automations pass look like?

Yes.

Saved as a routine, the Browserhub automations pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The product and engineering playbook catalogues the other recurring shapes of the site work, the Browserhub automations sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your Browserhub account and a companion works 1 operation in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide