Connect Adyntel to Borneo

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

View example

Assess privacy risks in a new ad campaign

When a campaign launch request arrives, use its supplied data-use details to create a Borneo DPIA for the processing activity.

View example

Register campaign data processing

Convert a supplied campaign data-use request into a Borneo processing activity record for privacy operations.

View example

Schedule a cloud scan for campaign data systems

On a recurring schedule, initiate a Borneo cloud resource scan for resources identified in the campaign data systems you specify.

View example

Review Borneo inspection results on a schedule

Periodically retrieve Borneo inspection results for the scan scope you specify and summarize findings that need attention.

View example

Export scan insights for campaign reviews

On a schedule, export filtered Borneo inspection insights for a specified scan so the team can review relevant findings alongside campaign work.

View example

Review the asset inventory for campaign systems

Periodically retrieve a filtered Borneo asset list for campaign-related systems and summarize inventory changes or gaps visible in the returned data.

View example

Export processing activities for campaign oversight

On a schedule, export Borneo processing activities using filters your team supplies and summarize records relevant to campaign oversight.

View example

Export recipients for campaign data reviews

Periodically export a filtered Borneo recipient list and summarize recipients relevant to the campaign data scope your team specifies.

View example

Set a risk threshold for campaign processing

When a campaign processing review request arrives with risk factors and an activity reference, create a Borneo threshold for that activity.

Supported Triggers and Actions

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

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