Connect Airwallex to Borneo

When something happens in Airwallex, 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

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

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Borneo

Scan after an Airwallex data change

Start a Borneo cloud resource scan when an Airwallex webhook reports a relevant change, then summarize the scan status.

Schedule a recurring finance data scan

Run a recurring Borneo scan on a schedule to review cloud resources associated with Airwallex financial operations.

Record a new finance operations asset

Create a Borneo asset record when a webhook reports a new system or resource supporting Airwallex operations.

Register a newly identified data recipient

Create a Borneo recipient record when a webhook identifies a new organization receiving data in an Airwallex-related process.

Review Airwallex-related recipients periodically

On a recurring schedule, filter Borneo recipients using the criteria you provide and summarize records needing review.

Start a breach impact assessment from an incident notice

Create a draft Borneo data breach evaluation when a webhook reports a suspected incident involving Airwallex-related data.

Summarize inspection findings for finance systems

On a schedule, retrieve Borneo inspection results for the scan scope you specify and highlight findings that need review.

Export a finance resource inventory for review

Create a scheduled Borneo inventory export using the resource filters and fields your team specifies.

Prepare a processing activity register export

Generate a recurring Borneo processing activities export for Airwallex-related processes using your supplied criteria.

Supported Triggers and Actions

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

Airwallex 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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13

Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit

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.