Connect Airwallex to Codemagic

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

When this happens · Trigger

Do this · Action

Adds an application from a private repository.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Codemagic

Build After a Funded Airwallex Payment

Start a Codemagic build when an Airwallex payment is confirmed, using a webhook request from your payment workflow.

Review Build History Alongside Settlement Checks

On a recurring schedule, retrieve Codemagic build history for a payment operations review and send a concise report to your chosen channel.

Add a Repository When a Project Is Funded

Use a Notis webhook tied to a funding milestone to add a repository URL to Codemagic when the project is ready for CI setup.

Review Codemagic Applications During Finance Close

Add a scheduled Codemagic application inventory to a recurring Airwallex finance close checklist, with run reports delivered to your selected channel.

Send an Approved Release Signal to Codemagic

After a release approval tied to your Airwallex operations, use a Notis webhook to send the supplied Git provider payload to Codemagic.

Check Build Cache Before Monthly Spend Review

Schedule a Codemagic cache inventory as a supporting input to a monthly Airwallex spend review, with the result sent to your selected report channel.

Retrieve Build IP Ranges for a Payment Integration Review

When a network access review starts, use a Notis webhook to retrieve Codemagic public IP ranges for whitelist planning around payment integrations.

Include Codemagic Team Apps in an Access Review

On a recurring schedule, list Codemagic team applications as context for an Airwallex operations access review and route the report to your chosen channel.

Supported Triggers and Actions

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

Airwallex triggers

Codemagic actions

Recurring trigger

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

TriggerScheduled

Add Application from Private Repository

Adds an application from a private repository.

ActionInstant

Webhook trigger

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

TriggerInstant

Add New Application

Adds a Git repository as an application.

ActionInstant

Get Meta Information

Retrieves metadata, including public IP addresses.

ActionInstant

Get Variable Group Information

Retrieves information about a variable group.

ActionInstant

Update Variable Group

Changes the name and security settings of a variable group.

ActionInstant

Delete All Application Caches

Deletes all cached data for an application.

ActionInstant

Delete Specific Cache

Deletes a specific cache from an application.

ActionInstant

Get All Builds

Lists builds for your applications.

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.