Connect ActiveMerge to Borneo

When something happens in ActiveMerge, 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 ActiveMerge to Borneo

View example

Scan cloud resources after a document release

Start a Borneo cloud resource scan when a document workflow signals that a release is ready for a privacy check.

View example

Review a Borneo scan iteration on a schedule

On a recurring schedule, retrieve a specified Borneo scan iteration's status, results, and metadata for a concise run report.

View example

Review inspection results when a scan signal arrives

Use a webhook signal to retrieve filtered Borneo inspection results for a scan or its pages.

View example

Export a Borneo scan insight page on a schedule

Periodically export filtered inspection results from a specified Borneo scan for review or record keeping.

View example

Register an approved legal document in Borneo

When a document workflow signals approval, create a legal document entry in Borneo with the details supplied in the request.

View example

Record a processing activity from a workflow request

Create a Borneo processing activity when a webhook request supplies the activity details for a new document or image process.

View example

Start a DPIA when a privacy review is requested

Create a Borneo data protection impact assessment for a specified processing activity when a review request reaches Notis.

View example

Review Borneo recipients on a recurring schedule

Retrieve a filtered Borneo recipients list on a schedule and surface the results in a Notis run report.

Supported Triggers and Actions

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

ActiveMerge 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.