Connect Airwallex to Botstar

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

When this happens · Trigger

Do this · Action

Generates a JavaScript callback snippet for when the live chat window closes.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Botstar

Turn Airwallex payment updates into BotStar support records

Create a BotStar CMS record when an Airwallex payment update arrives, so support can find the payment context in one place.

Refresh BotStar cash context from an Airwallex update

Update a BotStar bot attribute with an Airwallex cash position provided to a Notis webhook, giving the bot current finance context.

Keep BotStar payout guidance aligned with an Airwallex exception

When a payout exception arrives by webhook, update the relevant BotStar CMS item with the supplied status and guidance.

Add a BotStar finance FAQ attribute from an Airwallex update

Create a BotStar bot attribute for a new finance FAQ or policy detail supplied in an Airwallex related webhook request.

Create BotStar support attributes for an Airwallex payer

Create the BotStar user attributes needed to carry payer details into support conversations, based on an incoming Airwallex-related request.

Publish BotStar finance flow updates after an Airwallex review

Publish an approved BotStar finance flow to live after a review request arrives through a Notis webhook.

Supported Triggers and Actions

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

Airwallex triggers

Botstar actions

Recurring trigger

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

TriggerScheduled

BotStar LiveChat onClose Callback

Generates a JavaScript callback snippet for when the live chat window closes.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Bot

Creates a new bot.

ActionInstant

Get BotStar Application IDs

Retrieves the application IDs used by the live chat widget.

ActionInstant

Create Bot Attribute

Creates a bot attribute for shared, multilingual values.

ActionInstant

Livechat boot

Generates code to reinitialize the live chat widget after it loads.

ActionInstant

Create CMS Entity

Creates a content entity with optional custom fields.

ActionInstant

Close BotStar Livechat Widget

Generates a JavaScript snippet to hide the live chat window in livechat or popup mode.

ActionInstant

Create Entity Fields

Adds fields to an existing content entity.

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.