Connect Airwallex to Ably

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

When this happens · Trigger

Do this · Action

Queries presence details for multiple Ably channels in one request.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Ably

Broadcast Airwallex payment updates to Ably

Send Airwallex payment updates to an Ably channel so your team or connected tools can react in real time.

Share payout status changes in Ably

Publish Airwallex payout status changes to Ably so operations can spot progress or exceptions without repeatedly checking the dashboard.

Broadcast Airwallex FX updates to Ably

Send incoming Airwallex foreign exchange updates to an Ably channel used by your finance or product workflows.

Stream Airwallex card activity to Ably

Publish incoming Airwallex card activity to an Ably channel for timely visibility across finance and operations.

Log Airwallex transfer events in Ably

Publish incoming transfer events to an Ably channel to create a shared activity stream for teams and connected tools.

Push an Ably alert for Airwallex payment events

Send an Ably push notification when a relevant Airwallex payment event arrives, so you can notice it away from the dashboard.

Get an Ably push for payout exceptions

Send a push notification for incoming Airwallex payout events that match your stated exception criteria.

Route Airwallex finance events to Ably channels

Publish incoming Airwallex events to the relevant Ably channel based on the event's stated type or content.

Publish a daily Airwallex event brief to Ably

At a chosen time, publish a concise brief in Ably using Airwallex event data available to the automation from connected context.

Supported Triggers and Actions

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

Airwallex triggers

Ably actions

Recurring trigger

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

TriggerScheduled

Query Batch Presence

Queries presence details for multiple Ably channels in one request.

ActionInstant

Webhook trigger

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

TriggerInstant

Query Batch Presence History

Retrieves presence history for multiple Ably channels.

ActionInstant

Delete Channel Subscription

Unsubscribes a device or client from push notifications for one or all channels.

ActionInstant

Get Channel Details

Retrieves status and occupancy details for an Ably channel; requires channel metadata permission.

ActionInstant

Get Channel History

Retrieves a page of message history for an Ably channel.

ActionInstant

Get Channel Presence

Get the members currently connected and active on a channel.

ActionInstant

Get Channel Presence History

Retrieves the presence event history for a channel.

ActionInstant

Get Message Versions

Retrieves historical versions of a channel message, including updates and deletions.

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.