Refresh context upload details when work starts
Keep context upload credentials current when a new workflow needs them.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Browser Context
Tool to update a specific browser context. use when you need fresh upload url and encryption details for an existing context, after obtaining a valid context id.
Why this helps
Expired upload information can stop browser tasks that depend on custom user data.
- Request current upload details at the point of need.
- Reduce failures caused by stale context data.
- Keep the refresh step attached to the incoming request.
Setup
Build it in a few focused steps.
- 1Connect 0CodeKit and Browserbase tool in Notis once.
- 2Create an automation instructing Notis to update the supplied context id.
- 3Choose the webhook trigger.
- 4Select a report channel.
- 5Test with one real context refresh request.
Questions about this workflow
What must I provide?
Provide a valid Browserbase context id in the webhook request or automation prompt.
Does this create a new context?
No. It updates an existing context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 0CodeKit to Browserbase tool. A trigger fires from one place; an action lands in another.
0CodeKit triggers
Browserbase tool actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a new browser context
Tool to create a new browser context. use when you need to obtain upload credentials for a custom user-data-directory in a project.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve a browser context
Tool to retrieve details of a specific browser context. use when you have a context id and need its metadata.
Update Browser Context
Tool to update a specific browser context. use when you need fresh upload url and encryption details for an existing context, after obtaining a valid context id.
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
Retrieve a browser session
Tool to retrieve details of a specific browser session. use when you have a session id and need its metadata (status, urls, timestamps).
Retrieve Session Debug URLs
Tool to retrieve live debug urls for a specific session. use when you need to connect to a running session for debugging.
Download Session Artifacts
Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.
Retrieve Session Logs
Tool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.
Connect any two apps with Notis in the middle.
0CodeKit and Browserbase tool, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Browserbase tool.