Connect Airwallex to Detrack

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

When this happens · Trigger

Do this · Action

Add a pickup job.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Detrack

Reconcile Airwallex payments with delivery jobs

Review recent Airwallex payment activity against Detrack jobs and get a concise report of matches, gaps, and items needing review.

Find delivery jobs tied to settlement exceptions

Check Airwallex settlement activity against Detrack search results to identify jobs linked to payments that need attention.

Review delivery jobs after payment activity

Use recent Airwallex payment activity as context for a filtered Detrack job review, then report jobs that may require operational follow-up.

Prepare a daily list of payment-backed deliveries

Review Detrack deliveries for a chosen date alongside recent Airwallex payments and report records that satisfy your stated payment rule.

Prioritize delivery follow-up from cash activity

Use Airwallex cash activity and a stated priority rule to search Detrack for delivery jobs that deserve timely review.

Check delivery details for a transaction reference

Look up a Detrack job by delivery order number and date when Airwallex activity includes a matching reference, then report its current details.

Review collections against Airwallex payment activity

Review Detrack collection jobs alongside Airwallex payment activity and report collections with matching or missing references.

Verify a Detrack job from a finance reference

When a finance reference contains a Detrack delivery order number, retrieve the matching job and summarize its current status for review.

Search deliveries when a payment alert arrives

Start from an HTTP webhook request carrying a payment reference, search Detrack for related deliveries, and report possible matches.

Supported Triggers and Actions

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

Airwallex triggers

Detrack actions

Recurring trigger

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

TriggerScheduled

Add Collection

Add a pickup job.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete All Collections

Delete all collection jobs for a specific date.

ActionInstant

Bulk Create Depots

Creates multiple depots, each with a name and geocodable address.

ActionInstant

Delete All Deliveries

Delete all delivery jobs for a specific date.

ActionInstant

Create Depot

Creates a depot as a starting or ending point for delivery routes.

ActionInstant

Delete Delivery

Delete one or more delivery jobs.

ActionInstant

Edit Delivery

Update details of existing delivery jobs.

ActionInstant

Search

Searches delivery or collection jobs with pagination and ordering options.

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.