Connect Affinity to Browserbase tool
When something happens in Affinity, Notis takes the next step in Browserbase tool. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Affinity to Browserbase tool
Research a deal's website in an isolated browser
Start a browser session to inspect a company website linked to an Affinity deal and summarize useful public details.
Review tracked browser sessions on a schedule
Periodically list Browserbase sessions so Notis can surface active work that may need attention alongside your Affinity pipeline routine.
Inspect logs after deal research runs
Use a webhook request to retrieve a Browserbase session's logs and summarize browsing issues or useful network activity.
Retrieve artifacts from a completed deal research session
Request the artifact archive from a completed Browserbase session and have Notis report what was returned.
Update a browser session after a deal research request
Send a requested status update to a Browserbase session and report the outcome with its deal research context.
Check Browserbase project capacity before research
On a recurring schedule, retrieve Browserbase project details so Notis can summarize default timeout and assigned concurrency for planning research runs.
Review Browserbase usage for deal research
Retrieve Browserbase project usage statistics on a schedule and summarize browser minutes and proxy bytes consumed.
Inspect a saved browser context for a deal workflow
Retrieve metadata for a specified Browserbase context when you need to understand which reusable context a research task is using.
Refresh upload details for a research context
Request fresh upload URL and encryption details for an existing Browserbase context when a research flow needs to upload user data.
Supported Triggers and Actions
Notis builds workflows that link Affinity to Browserbase tool. A trigger fires from one place; an action lands in another.
Affinity triggers
Browserbase tool actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Contexts create
Deprecated compatibility action for creating a browser context.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Contexts get
Deprecated compatibility action for retrieving a browser context.
Update Browser Context
Updates a browser context to provide fresh upload and encryption details.
Create Browser Session
Deprecated action for creating a browser session.
Create Browser Context
Creates a reusable browser context.
Create Browser Session
Creates an isolated browser session and returns its connection details.
Download Session Artifacts
Downloads a completed session’s generated files as a ZIP archive.
Delete a browser context
Permanently deletes a browser context and all its stored data.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Affinity and Browserbase tool
Connect any two apps with Notis in the middle.
Affinity 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.