Connect Affinda to Borneo

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

View example

Register parsed privacy documents in Borneo

Turn an Affinda-parsed privacy policy or data processing agreement into a Borneo legal document entry for review and tracking.

View example

Record invoice-derived assets for review

Use details extracted from an asset-related invoice to create a Borneo asset record for the team to verify.

View example

Capture contract recipients in Borneo

Create a Borneo recipient record from counterparty details extracted from a contract, with uncertain details flagged for review.

View example

Draft processing activities from extracted documents

Use Affinda-extracted processing details to create a Borneo processing activity, leaving unsupported information for review.

View example

Start a DPIA when extracted documents indicate risk

When an Affinda-processed document indicates a high-risk processing activity, create a Borneo DPIA record for assessment.

View example

Route uncertain privacy documents into a review record

Create a Borneo legal document entry for extracted privacy paperwork that needs a human to confirm its type or details.

View example

Triage the privacy document backlog

On a recurring schedule, review available Affinda-extracted privacy documents and create Borneo legal document entries for those not yet registered.

View example

Review extracted contracts for missing recipients

On a recurring schedule, look for Affinda-extracted contracts with recipient details that are not yet reflected in Borneo.

View example

Build a processing activity intake queue

Periodically find Affinda-extracted documents that describe processing activities and create Borneo records for the ones not yet tracked.

Supported Triggers and Actions

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

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