Connect Airwallex to Canny

When something happens in Airwallex, Notis takes the next step in Canny. 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 tag to a post.

Build an automation Browse examples

Examples

Ways Notis can move work from Airwallex to Canny

Turn Airwallex payment issues into Canny posts

Create a Canny feedback post when an Airwallex webhook reports a payment problem that needs product review.

Add payout context to an existing Canny post

Add a comment to a matching Canny post when an Airwallex webhook reports a payout event with useful product context.

Update Canny status for a reported FX issue

Change the status of a matching Canny post when an Airwallex webhook carries a meaningful foreign exchange issue update.

Tag Canny posts linked to Airwallex card issues

Apply an existing Canny tag to a matching post when a webhook reports an Airwallex card issue relevant to that feedback.

Publish a Canny changelog entry for an Airwallex update

Create a Canny changelog entry when a webhook carries approved product update details tied to Airwallex.

Review Airwallex activity for recurring product feedback

On a schedule, review available Airwallex activity for recurring product issues and find related Canny posts for triage.

Audit Canny tags on Airwallex related feedback

Periodically inspect Canny tags and identify Airwallex related feedback posts that may need consistent categorization.

Refresh Canny post details with available Airwallex context

Periodically identify Canny posts whose details may need relevant Airwallex context and update only clear matches.

Review Canny boards for Airwallex feedback routing

On a schedule, list Canny boards and report which ones appear relevant for Airwallex related product feedback.

Supported Triggers and Actions

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

Airwallex triggers

Canny actions

Recurring trigger

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

TriggerScheduled

Add Post Tag

Adds an existing tag to a post.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete User

Deletes a user and their comments and votes; some posts may also be removed.

ActionInstant

Change Post Status

Changes a post’s status and can notify voters.

ActionInstant

Create Changelog Entry

Creates a changelog entry and can publish it or notify users.

ActionInstant

Create Comment

Posts a new comment on a post.

ActionInstant

Create or Update User

Creates or updates a Canny user; an admin's email, name, and avatar cannot be changed via the API.

ActionInstant

Create Post

Creates a feature request or feedback post on a board.

ActionInstant

Create Tag

Creates a tag for categorizing posts.

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.