Codex
Bring live web data into your Codex tasks.

Connect live web data to your apps and AI tools.
Bring live web data into your Codex tasks.
Send scraped data into your Make scenarios.
Run your BrowserAct Bots from Claude Code.
Run Bots and retrieve results over HTTP.
Put fresh web data to work in WorkBuddy.
Add web data to your n8n workflows.
Use web data alongside your code.
Control a browser in your agent environment.
Send scraped data into your Make scenarios.
Add web data to your n8n workflows.
Move Bot results between your apps.
Bring live web data into your Codex tasks.
Run your BrowserAct Bots from Claude Code.
Put fresh web data to work in WorkBuddy.
Use web data in your everyday work.
Give your OpenClaw tasks fresh web data.
Add your web scrapers to Manus tasks.
Run your Bots from your AI workspace.
Bring website data into your research.
Use fresh web data in Genspark tasks.
Use web data alongside your code.
Call your Bots from Copilot Chat.
Connect your Bots to your development work.
Add web scraping tools to TRAE.
Bring website data into your Qoder workspace.
Use your Bots in Kiro development tasks.
Give CodeBuddy access to your web scrapers.
Run BrowserAct Bots from Cline.
Connect your Bots to Devin, formerly Windsurf.
Add your web scrapers to Kilo Code.
Use web data in your JetBrains workflow.
Connect your web scrapers to Augment.
Bring BrowserAct tools into Zed.
Collect web data from your terminal.
Run BrowserAct Bots from OpenCode.
Add web data tools to Qwen Code.
Use your web scrapers from Kimi Code.
Run Bots and retrieve results over HTTP.
Receive task results and status callbacks.
Run published Cloud Bots from AI clients.
Control a browser in your agent environment.
Export files from a Workflow Bot’s Output Data node.
| Product | Price | Availability |
|---|---|---|
| Studio Wireless | $129.00 | In stock |
| Air Pro | $89.00 | In stock |
| Travel ANC | $159.00 | Out of stock |
Schedule a tested Bot with Make.
Read scheduling guideCollect product fields with BrowserAct. Use Make to add them to Google Sheets.
Use Make, n8n, or Zapier to pass cloud Bot results to other apps. Use REST API for a custom application, MCP to expose cloud Bots as AI tools, or Agent CLI for browser control in your own agent environment.
MCP lets a compatible client discover and run published BrowserAct cloud Bots. Agent CLI gives your own agent commands to interact with a browser. Their execution environments and setup requirements are different.
No. The labels show the connection method. Multiple clients can use the same BrowserAct MCP Server or Agent CLI. Follow the guide for the transport, authentication, and features supported by your client.
The Google Sheets example uses Make. BrowserAct collects the data; Make maps the completed output to spreadsheet columns. For file-based delivery, Workflow Bots can export CSV or JSON through the Output Data node.
The task callbacks shown here notify your endpoint about results or status changes. Start the Bot through the API or a supported platform, then use its task status, result endpoint, or configured callbacks.
For a cloud Bot connection, first prepare a tested, published Bot and the credentials required by your chosen integration. MCP requires a configured server and an exposed tool. For Agent CLI, follow the CLI and Skill installation requirements.