Docs / Skills / Browser automation

Browser automation skill

When a site has no API, CloudyBot can still execute flows you approve: login (with your session), export, pricing checks, and more.

How to enable

1. Normal chat already includes the cloud browser for typical workflows—open a session when the UI prompts you.
2. For Specialists, enable browser tools on the thread when a duty requires navigation, forms, or screenshots.

What you can ask

Copy a line below and tune names, channels, or file titles to match your workspace.

• “Log into our admin, export this week’s signups CSV, and save it in my workspace.”
• “Go to {URL}, fill the form with these values, and confirm submission.”
• “Screenshot this page at phone, tablet, and desktop widths.”
• “Check pricing for these SKUs on {site} and put results in a table.”
• “Walk through our signup as a new user and report anything broken.”

Common pitfalls

• Sites with aggressive bot blocking may fail—have a fallback.
• Always use non-production accounts when testing destructive flows.

See also

• AI web automation (overview)