Connect Airwallex to Chmeetings

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

When this happens · Trigger

Do this · Action

Invite a new attendee to a meeting.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Chmeetings

Add a Donor After an Airwallex Gift

When an Airwallex donation arrives, create a ChMeetings person record for the donor if the webhook includes their name and contact details.

Flag Refunded Gifts for Donor Follow-up

Use an Airwallex refund webhook to update a known ChMeetings person with relevant contact information, or send a report for a human to decide what follow-up is appropriate.

Alert Your Team About a Large Gift

When an Airwallex gift meets a threshold you define, send a ChMeetings notification so the right team can review it promptly.

Schedule a Meeting After a Fundraising Milestone

When an Airwallex webhook reports a fundraising milestone you define, create a ChMeetings meeting for the follow-up discussion.

Create a Reminder to Review a Payout

When an Airwallex payout webhook arrives, schedule a ChMeetings reminder to review it if that reminder belongs in your team's ChMeetings process.

Alert on a Failed Gift Payment

Send a ChMeetings notification when an Airwallex webhook identifies a failed gift payment, so your team can decide whether follow-up is appropriate.

Review Donation Follow-up Reminders

On a schedule, list ChMeetings reminders and compare them with Airwallex donation activity supplied or made available to the automation, reporting possible follow-up gaps.

Review Donor Records Against Payment Activity

On a schedule, list ChMeetings people and compare available Airwallex gift activity to identify potential donor records that need human review.

Review ChMeetings Organizations for Finance Follow-up

On a schedule, list ChMeetings organizations and report directory information relevant to finance or fundraising coordination alongside available Airwallex context.

Supported Triggers and Actions

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

Airwallex triggers

Chmeetings actions

Recurring trigger

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

TriggerScheduled

Invite Meeting Attendee

Invite a new attendee to a meeting.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Attendee Details

Retrieves an attendee’s details by attendee ID.

ActionInstant

ChMeetings: Create Meeting

Create and schedule a meeting.

ActionInstant

ChMeetings: Create Organization

Create a new organization.

ActionInstant

ChMeetings: Create Reminder

Create a reminder for a meeting.

ActionInstant

Delete Meeting Attendee

Remove an attendee from a meeting.

ActionInstant

List Meeting Attendees

Lists attendees for a meeting, with optional pagination.

ActionInstant

ChMeetings: Delete Meeting

Permanently delete an existing meeting.

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.