Connect Addresszen to Browserless

When something happens in Addresszen, Notis takes the next step in Browserless. 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 Addresszen to Browserless

View example

Check a shipping page with a verified address

Use an address supplied through a webhook to inspect a shipping page and return the delivery options it displays.

View example

Check whether a service area accepts an address

Send a validated location and a service-area page through a webhook, then ask Browserless to inspect the page's response.

View example

Capture address form guidance from a website

Fetch a specified page's HTML after a validated address arrives, so Notis can summarize its address-entry requirements.

View example

Save a visual check of address checkout

Capture a screenshot of a specified checkout page after a webhook request includes a validated delivery address and page.

View example

Create a PDF record of delivery details

Generate a PDF from a specified delivery page when a webhook supplies a validated address and the page URL.

View example

Download a receipt from an address request

Run a specified browser flow to download a file, then report the downloaded artifact in connection with the validated address request.

View example

Review a protected location page

Use Browserless's protected-content action to retrieve HTML from a specified page supplied with a validated location request.

View example

Review delivery pages on a schedule

On a recurring schedule, inspect a user-supplied list of delivery pages and summarize their current visible content.

View example

Refresh address instructions from key sites

Fetch HTML from a user-supplied list of address instruction pages on a schedule and summarize relevant guidance.

Supported Triggers and Actions

Notis builds workflows that link Addresszen to Browserless. A trigger fires from one place; an action lands in another.

Addresszen triggers

Browserless actions

Recurring trigger

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

TriggerScheduled

Download file using Puppeteer script

Downloads files saved by Chrome during a browser automation script.

ActionInstant

Webhook trigger

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

TriggerInstant

Execute Custom Function

Runs a custom browser automation script.

ActionInstant

Fetch HTML Content

Fetches a webpage’s complete HTML content, including dynamic content.

ActionInstant

Generate PDF from webpage

Generates a PDF from a webpage.

ActionInstant

Scrape webpage content using CSS selectors

Extracts structured content from selected webpage elements.

ActionInstant

Take Screenshot

Captures a screenshot of a webpage.

ActionInstant

Unblock Protected Content

Retrieves webpage content from sites protected against automated access.

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.