Connect Airwallex to Dynamics365

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

When this happens · Trigger

Do this · Action

Retrieves one page of Dynamics 365 invoices.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Dynamics365

Turn settled Airwallex payments into Dynamics invoices

Create a Dynamics invoice from an Airwallex payment notification, using the supplied customer and line item details.

Create Dynamics leads from Airwallex customer signals

Use an incoming Airwallex request with explicit prospect details to create a Dynamics lead for timely follow-up.

Add Airwallex business contacts to Dynamics

Create a Dynamics contact when a webhook carries verified business contact details from an Airwallex workflow.

Attach payment issue context to a Dynamics record

Create a Dynamics note with Airwallex payment issue details and link it to a supported record when its identity is supplied.

Create Dynamics follow-up tasks for payout exceptions

Turn a supplied payout exception and owner or due date context into a Dynamics task for follow-up.

Prepare a monthly Dynamics invoice review from Airwallex context

On a schedule, retrieve Dynamics invoices and create a review note using the Airwallex finance context you provide.

Review Dynamics leads alongside Airwallex cash context

Schedule a bounded lead review and summarize it alongside finance context provided by your team.

Find Dynamics invoices that need a human follow-up

On a schedule, retrieve Dynamics invoices and summarize review priorities using follow-up criteria supplied by your team.

Create Dynamics opportunities from funded expansion signals

Create a Dynamics opportunity when a webhook includes a clear expansion signal and the customer context to support it.

Supported Triggers and Actions

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

Airwallex triggers

Dynamics365 actions

Recurring trigger

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

TriggerScheduled

Get all invoices action

Retrieves one page of Dynamics 365 invoices.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Annotation

Creates a text or attachment note, optionally linked to a supported record.

ActionInstant

Add Contact to Account

Links an existing contact to an existing account, replacing the contact’s current parent customer.

ActionInstant

Create Account

Create a new account record.

ActionInstant

Create Email Activity

Creates and stores a draft email activity without sending the email.

ActionInstant

Assign User Security Role

Assigns a security role to a system user; requires administrator privileges and changes their permissions.

ActionInstant

Create Case

Creates a new case in Dynamics CRM.

ActionInstant

Create Product

Creates a catalog product and returns its selected representation.

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.