Connect Adtraction to Browserbase tool

When something happens in Adtraction, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Adtraction to Browserbase tool

View example

Review affiliate partner status weekly

Open your Adtraction partner view on a schedule and summarize visible status changes for a quick weekly review.

View example

Review a partner page on demand

Send a webhook to start a Browserbase session that reviews a specified Adtraction partner page and returns a concise summary.

View example

Inspect affiliate browser session activity

On a schedule, retrieve Browserbase session logs to help review network activity from an Adtraction browser run.

View example

Retrieve artifacts from an affiliate browser run

Use a webhook to download artifacts from a completed Browserbase session used for an Adtraction review.

View example

Check affiliate browser sessions

List Browserbase sessions on a schedule and summarize their status so unfinished Adtraction runs are easier to spot.

View example

Request early completion for a browser run

Send a webhook to request completion of a specific Browserbase session when its Adtraction task is done early.

View example

Review details for a specific affiliate browser run

On a schedule, retrieve metadata for a known Browserbase session and report its status, URLs, and timestamps.

View example

Get debug access for an active browser run

Start a webhook workflow to retrieve debug URLs for a specific active Browserbase session when an Adtraction task needs inspection.

Supported Triggers and Actions

Notis builds workflows that link Adtraction to Browserbase tool. A trigger fires from one place; an action lands in another.

Adtraction triggers

Browserbase tool actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Contexts create

Deprecated compatibility action for creating a browser context.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Contexts get

Deprecated compatibility action for retrieving a browser context.

ActionInstant

Update Browser Context

Updates a browser context to provide fresh upload and encryption details.

ActionInstant

Create Browser Session

Deprecated action for creating a browser session.

ActionInstant

Create Browser Context

Creates a reusable browser context.

ActionInstant

Create Browser Session

Creates an isolated browser session and returns its connection details.

ActionInstant

Download Session Artifacts

Downloads a completed session’s generated files as a ZIP archive.

ActionInstant

Delete a browser context

Permanently deletes a browser context and all its stored data.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.