Connect 2chat to Cloudflare browser rendering

When something happens in 2chat, Notis takes the next step in Cloudflare browser rendering. 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 2chat to Cloudflare browser rendering

View example

Turn WhatsApp page links into a page brief

When a 2chat message includes a page URL, capture its rendered content and screenshot so Notis can summarize the page for a quick reply.

View example

Look up specific details on a page from WhatsApp

Use a URL and a requested detail from a 2chat message to scrape matching page elements and return what they contain.

View example

Check how a shared page looks

Capture a screenshot of a URL shared in a 2chat message so you can review the page's visible state before replying.

View example

Review a competitor page shared in chat

Capture rendered content and a screenshot of a competitor URL shared through 2chat, then summarize the visible offer and page messaging.

View example

Pull contact details from a shared webpage

When a 2chat message shares a public contact or company page, scrape relevant page elements and summarize the details visible there.

View example

Check a page link before replying

Snapshot a public URL from a 2chat message and report whether browser rendering returned page content and a screenshot.

View example

Find product facts on a linked page

Use a product URL and a question from a 2chat message to scrape relevant page elements and return the visible product details.

View example

Preview a shared page at a chosen viewport

Capture a screenshot of a URL shared in 2chat using a requested viewport, so you can inspect how the page appears at that size.

View example

Review saved WhatsApp links on a schedule

On a recurring schedule, snapshot a user-provided list of public URLs collected from 2chat and summarize the rendered pages.

Supported Triggers and Actions

Notis builds workflows that link 2chat to Cloudflare browser rendering. A trigger fires from one place; an action lands in another.

2chat triggers

Cloudflare browser rendering actions

Recurring trigger

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

TriggerScheduled

Capture Screenshot

Tool to capture a webpage screenshot. Use when you need a visual snapshot of a URL or HTML with optional viewport and clipping.

ActionInstant

Webhook trigger

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

TriggerInstant

List Accounts

Tool to list all Cloudflare accounts accessible. Use to retrieve a valid account_id for further browser rendering actions.

ActionInstant

Scrape HTML Elements

Tool to scrape HTML elements for text, HTML, attributes, and box metrics. Use when you need detailed data of matched selectors after rendering a page.

ActionInstant

Take Webpage Snapshot

Tool to capture rendered HTML and screenshot of a webpage. Use when you need both DOM content and an image in one request with custom loading and capture settings.

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.