Connect AimTell to Borneo

When something happens in AimTell, Notis takes the next step in Borneo. 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 Borneo

View example

Scan Cloud Data Behind Push Campaigns

Schedule a Borneo cloud scan to look for sensitive data in systems used to manage AimTell campaigns and subscribers.

View example

Review Data Findings Before a Push Campaign

Use a webhook to ask Borneo for filtered inspection results when a campaign review needs a closer look at discovered data.

View example

Check Borneo Scan Progress Automatically

On a schedule, retrieve the status and metadata for a specific Borneo scan iteration so follow-up does not depend on memory.

View example

Export Insights for a Push Data Review

Request a Borneo insight export for a scan when a specific AimTell-related data review needs a shareable evidence set.

View example

Refresh a Sensitive Resource Inventory

Schedule Borneo exports of filtered leaf resources to support recurring reviews of cloud resources used in push notification operations.

View example

Start a Breach Impact Evaluation from an Incident Request

When an incident request arrives, create a Borneo breach impact evaluation using the details supplied for review.

View example

Register a Data Recipient from a Review Request

Create a detailed Borneo recipient record when a request identifies a new entity that receives or processes data for AimTell operations.

View example

Find Recipients Relevant to a Campaign Review

Retrieve a filtered Borneo recipient list when a push campaign review needs to identify relevant data recipients.

View example

Prepare a Recurring Recipient Review Export

Generate a filtered Borneo recipient export on a schedule so vendor and data recipient reviews have a ready starting point.

Supported Triggers and Actions

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

AimTell triggers

Borneo actions

Recurring trigger

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

TriggerScheduled

Access scan iteration by id

Retrieves the status, results, and details of a scan iteration.

ActionInstant

Webhook trigger

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

TriggerInstant

Add discovered recipients

Adds previously discovered recipients to the confirmed recipient list.

ActionInstant

Archive discovered recipient

Archives a discovered recipient and their information.

ActionInstant

Delete data breach by id

Irreversibly deletes a data breach evaluation record.

ActionInstant

Create and schedule cloud resource scan

Creates and schedules a scan of cloud resources.

ActionInstant

Create dashboard user

Creates a dashboard user account with assigned access.

ActionInstant

Create department with translations

Creates a department with translated information.

ActionInstant

Create domain with polling frequency

Creates a domain with an automatic polling frequency.

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.