Keep browser logs close to changing task context
Every meaningful task update can bring the browser evidence needed for the next decision.
Trigger
Task Updated
Triggers when a task is updated. Fires for every kind of update on the task, including comments. If you only care about a specific property changing, prefer the dedicated trigger (`CLICKUP_TASK_STATUS_UPDATED`, etc.) — those are pre-filtered by ClickUp and produce less traffic. `changes[]` can carry any FieldChange variant (`StatusChange`, `PriorityChange`, `AssigneeAddChange`, `AssigneeRemoveChange`, `TagAddChange`, `TagRemoveChange`, `DueDateChange`, `TimeEstimateChange`, `TimeSpentChange`, `NameChange`, `ContentChange`, `CommentChange`, `CustomFieldChange`).
Action
Retrieve Session Logs
Tool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.
Why this helps
Task changes and browser activity live in separate places, making investigation slow.
- Speed up investigation
- Keep task and browser evidence together
- Reduce context switching
Setup
Build it in a few focused steps.
- 1Connect Clickup and Browserbase tool in Notis once.
- 2Create an automation that retrieves logs for the Browserbase session linked to the updated task.
- 3Pick Clickup Task Updated as the trigger.
- 4Choose a report channel and test by editing one task with an active session.
Questions about this workflow
Why use the broad Task Updated trigger?
Use it when any task change should prompt a browser log review.
Can I limit it to one property?
Use a dedicated ClickUp trigger when the relevant property has one, such as status or priority.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clickup to Browserbase tool. A trigger fires from one place; an action lands in another.
Clickup 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.
Folder Created
Triggers when a new Folder is created.
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.
Folder Deleted
Triggers when a Folder is deleted.
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
Folder Updated
Triggers when a Folder is updated (renamed, content edited, etc.).
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).
List Created
Triggers when a new List is created.
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.
List Deleted
Triggers when a List is deleted.
Download Session Artifacts
Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.
List Updated
Triggers when a List is updated (renamed, content edited, etc.).
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.
Clickup 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.