Connect Airwallex to Apify

When something happens in Airwallex, Notis takes the next step in Apify. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Creates a new Actor with the specified configuration.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Apify

Research a New Airwallex Payee

When an Airwallex payment alert arrives, run an Apify Actor to gather public information about the payee for a quick review.

Research a Market After a Large Receipt

Use a receipt alert to run an Apify Actor and collect public market information related to the business context you provide.

Run a Competitor Watch Task on a Schedule

On a recurring schedule, run a configured Apify task to collect competitor updates relevant to your business.

Check Supplier Prices on a Schedule

Run a configured Apify task on a schedule and retrieve its dataset items to review supplier pricing changes.

Research a Payout Destination on Demand

When a payout webhook request arrives, run an Apify task with supplied input to collect relevant public destination context.

Review the Latest Apify Run Monthly

On a schedule, retrieve the latest run for a selected Apify Actor to keep a recurring collection process visible.

Review Your Apify Actor Inventory

On a schedule, retrieve your Apify Actor list and review which Actors support your ongoing business research.

Run an Expense Research Task Immediately

Start a prepared Apify task synchronously when a webhook request arrives and return its output for an expense-related research question.

Collect Public Risk Signals on a Schedule

Run a prepared Apify task regularly and retrieve its dataset items for a human review of public risk signals relevant to your business.

Supported Triggers and Actions

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

Airwallex triggers

Apify actions

Recurring trigger

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

TriggerScheduled

Create Actor

Creates a new Actor with the specified configuration.

ActionInstant

Webhook trigger

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

TriggerInstant

Get user builds list

View a paginated history of a user’s builds across all actors.

ActionInstant

Create Dataset

Creates a new dataset.

ActionInstant

Abort Actor Build

Abort an Actor build that is starting or running; terminal builds are unaffected.

ActionInstant

Create Actor Task

Creates an Actor task for later runs.

ActionInstant

Delete Actor Build

Permanently delete an Actor build; the Actor’s default build cannot be deleted.

ActionInstant

Create Task Webhook

Creates a webhook to notify external systems about task runs.

ActionInstant

Get Actor Build

Retrieves details and status for a specific Actor build.

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.