Connect Airwallex to Bugherd

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

When this happens · Trigger

Do this · Action

Adds an existing guest or invites a new client to a project.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Bugherd

Turn Airwallex payment failures into BugHerd tasks

Create a BugHerd task when an Airwallex payment failure needs investigation, with the available payment details and next step.

Add payout delay context to a BugHerd task

When an Airwallex payout notification relates to an existing BugHerd task, add the latest supplied details as a comment.

Track an Airwallex FX discrepancy for review

Create a BugHerd task from a webhook notification about a foreign exchange discrepancy, using only the values supplied.

Route Airwallex card incidents to BugHerd

Turn a card-related incident notification into a BugHerd task so the team can track investigation and follow-up.

Append Airwallex account review updates

Add incoming account review updates to the matching BugHerd task as a comment, keeping the history in context.

Create BugHerd tasks for unresolved payment reviews

On a recurring schedule, review available Airwallex payment information and create tasks for unresolved items that meet your criteria.

Review BugHerd payment tasks against Airwallex updates

On a schedule, review tasks in a specified BugHerd project and use available Airwallex updates to identify payment follow-up candidates.

Add scheduled payout review notes to BugHerd

Review available payout information on a schedule and add a concise update to a matching existing BugHerd task.

Scan BugHerd for open FX exception follow-ups

On a schedule, list tasks in a BugHerd project that match your FX exception criteria and review them alongside available Airwallex data.

Supported Triggers and Actions

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

Airwallex triggers

Bugherd actions

Recurring trigger

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

TriggerScheduled

Add Guest to Project

Adds an existing guest or invites a new client to a project.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Member to Project

Adds a member to a project.

ActionInstant

Create Attachment

Adds an attachment from a URL to a task.

ActionInstant

Create Column

Creates a custom workflow column in a project.

ActionInstant

Create Comment

Adds a comment to a task.

ActionInstant

Create Project

Creates a new project.

ActionInstant

Create Task

Creates a task in a project.

ActionInstant

Create Webhook

Creates a webhook for real-time task or comment notifications.

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.