Connect 21risk to Bugbug

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

View example

Run a Bugbug smoke test after a 21risk checklist change

Start a focused Bugbug test whenever a 21risk checklist update arrives by webhook, then report the run outcome.

View example

Review Bugbug runs when a 21risk action is assigned

When a 21risk action assignment is posted to a webhook, fetch relevant Bugbug run details and summarize release risk.

View example

Find Bugbug tests for a new 21risk control

Search the Bugbug test catalog when a 21risk control is created and return likely validation tests for review.

View example

Check Bugbug suites for 21risk audit coverage

When an audit scope arrives from 21risk, list Bugbug suites and summarize which suites appear relevant or absent.

View example

Reproduce a 21risk finding with Bugbug

Trigger a named Bugbug test from a 21risk finding webhook and return execution details for the remediation team.

View example

Add Bugbug evidence to 21risk remediation updates

Fetch Bugbug run details when a 21risk remediation update arrives and summarize whether evidence supports closure.

View example

Discover regression tests for a 21risk checklist revision

Search Bugbug tests after a checklist revision and return candidates that can validate the changed requirement.

View example

Review Bugbug test health for open 21risk work

On a schedule, retrieve Bugbug run details and summarize test health relevant to open 21risk compliance work.

View example

Run a scheduled Bugbug control smoke test

Run a defined Bugbug test on a recurring schedule to maintain evidence for a 21risk control.

Supported Triggers and Actions

Notis builds workflows that link 21risk to Bugbug. A trigger fires from one place; an action lands in another.

21risk triggers

Bugbug actions

Recurring trigger

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

TriggerScheduled

Get test run details

Get detailed information about test runs from bugbug. this action retrieves test run details with optional filtering parameters.

ActionInstant

Webhook trigger

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

TriggerInstant

List suites

List all available test suites in the bugbug platform. this tool makes a get request to the /suites/ endpoint and returns a list of available test suites with pagination support.

ActionInstant

List tests

Retrieves a list of all available tests in the bugbug account. this action provides access to all tests in the account with pagination support. it returns basic information about each test including its id, name, description, and timestamps.

ActionInstant

Run test

Execute a test in bugbug and return the test run details. this action allows you to run a specific test with optional configuration for browser, device, viewport, and variable overrides. it returns detailed information about the test run including step-by-step execution status.

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.