Build with TabWorker.
Start with the public integration docs and apply for a private integration. Production access is reviewed manually; public SDK packages are still planned.
Apply for developer access →Developer documentation
Meet TabWorker Relay
A helping hand
in your browser.
If an app sent you here, it uses TabWorker Relay to carry out tasks in Chrome with your permission. Your app guides the work. Relay works in the tabs you approve.
Your browser. Your permission. Pause and Stop are right in the extension.
Why your app brought you here
Your app knows the task.
Relay gives it a way to help.
Some tasks take you beyond an app and into other websites. Developers use TabWorker to connect their workflows to those sites in your own browser, where you’re already signed in.
- 01 / The task
Your app
You ask your app to do something. It provides the workflow and guides the steps.
- 02 / The connection
TabWorker Relay
The Chrome extension carries out approved browser steps and returns page information to your app.
- 03 / Where the work happens
Your browser
The websites you already use, in your own Chrome. You review and approve the access.
Your app remains responsible for its workflow and how it handles your data. Relay provides the browser connection and controls for approved access.
How it gets to work
You decide when
the work starts.
Installing the extension or entering a connection code alone does not give an app page access. Review the request before allowing it to work in your browser.
See the connection steps →- InstallGet Relay from its official Chrome Web Store listing.
- ConnectEnter the connection code provided by your app.
- ReviewSee who’s asking, the task, the requested access, and where page data will go.
- AllowChoose the tab and approve the access. You can pause or stop from Relay.
Control you can see
Know what you’re allowing.
Choose the access. Review the task, sites, actions, and expiry before approving. Relay’s permission controls limit browser work to the access you allow.
See what’s shared. Approved tasks can send URLs, page content, form state, screenshots, and results to your connected app. Screenshots may contain personal information. Read its data practices and our privacy policy.
Stop from your browser. Pause a task, stop it, or use Stop all. Stop blocks further actions and page access and discards late results. It cannot undo completed actions or recall data already sent.
Before you connect
A few fair questions.
Browser access deserves a clear explanation. Here are the details behind the connection.
Read the full privacy policy ↗Why does my app use TabWorker?
Your app’s developer creates the workflow: what the task should do and how it should proceed. TabWorker provides a browser connection, access review, and local controls that the developer can integrate into that experience. It lets your app help on other websites while you keep using your own Chrome.
Can Relay read my whole browser?
Connecting an app alone gives it no page access. Browser work is limited by the tabs, sites, actions, and expiry you approve in Relay. Other access needs authorization. Relay does not export your browser profile or cookie jar; approved page content and screenshots can still contain sensitive information.
Why does Chrome mention “debugging”?
Chrome calls the browser-control permission “debugger.” Relay uses it to interact with and observe approved tabs, including clicking, entering text, navigating, and taking screenshots. Chrome displays an indicator while it is attached. Review the permissions on the official Store listing and the access request in Relay before proceeding.
Who receives information from a task?
Your connected app receives approved page information and results. TabWorker handles connection records and, for tasks hosted by TabWorker, may also retain task details and page summaries. Your app may use its own hosting or model providers. Read our privacy policy and your app’s disclosures for recipients, storage, and deletion practices.
Is browser data used for ads or AI training?
Our privacy policy prohibits using Relay content for advertising, resale, unrelated profiling, or general-purpose model training. Production developers must meet these restrictions. An app may use a model provider to carry out your requested task; check its disclosed recipients and data practices.
What if I need help or want my data deleted?
Email team@tabworker.com for TabWorker support, privacy questions, or access and deletion requests. For your app’s task results, charges, or records, contact its support team too. Stopping a task or uninstalling Relay does not delete information already sent.
When you’re ready
Connect from the app you’re using.
Install Relay, then return to your app for its connection code and task instructions. Review the requested access before you allow it.
Building an app?
Give your app a browser.
Bring the workflow you know how to build. Keep your own code and customer experience, and let Relay connect it to the browser access your customers approve.
Publishing is optional. Your original workflows remain yours. Each Boonwerks partnership has its own agreed services and commercial terms.