Connect AimTell to Bugbug

When something happens in AimTell, 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 AimTell to Bugbug

View example

Run a Bugbug smoke test before an AimTell campaign

Start a Bugbug test when a campaign launch request arrives, so key site flows get checked before subscribers receive a push.

View example

Check Bugbug results after an AimTell campaign test

When a campaign-related test run needs review, fetch its Bugbug details and summarize the outcome for your team.

View example

Review Bugbug tests used for AimTell campaign pages

On a recurring schedule, list Bugbug tests and surface the campaign-page checks that may need an owner or cleanup.

View example

Get a scheduled catalog of Bugbug campaign test suites

Receive a recurring list of Bugbug suites so campaign owners can quickly find the right group of site checks.

View example

Test a push campaign destination when it is submitted

Send a destination check request to Notis and run the chosen Bugbug test against the page flow your team wants to validate.

View example

Summarize a Bugbug regression run for campaign owners

When a run is flagged for campaign review, fetch its details and summarize the execution status and failed steps for the owner.

View example

Review recent Bugbug runs on a campaign QA schedule

On a recurring schedule, retrieve run details for the Bugbug tests you specify and highlight results that still need follow-up.

View example

Run a subscriber journey test from a campaign review request

Start a Bugbug journey test from a review request so your team can check the subscriber path before a push campaign is sent.

Supported Triggers and Actions

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

AimTell 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

Retrieves detailed information about test runs.

ActionInstant

Webhook trigger

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

TriggerInstant

List suites

Lists all available test suites.

ActionInstant

List tests

Lists the available tests in your account.

ActionInstant

Run test

Runs a test and returns its status and details.

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.