Turn Airwallex payment exceptions into callback requests
Get a callback request ready when a payment exception needs a conversation, with the payment context close at hand.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create callback
Queues a callback request for an agent at a call center to handle.
Why this helps
Payment exceptions can sit unnoticed while you look up the customer and remember to call.
- Create a callback request from an incoming exception notification.
- Keep the supplied payment context with the follow-up instruction.
- Reduce the chance that a customer call gets lost in a busy day.
Setup
Build it in a few focused steps.
- 1Connect Airwallex and Dialpad once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what to automate from any channel.
- 3In one instruction, ask Notis to create a Dialpad callback for an Airwallex payment exception, using a phone number supplied in the webhook and including the provided context.
- 4Choose the Notis webhook trigger and choose where run reports should go.
- 5Test with one real example that includes a reachable phone number and exception details.
Questions about this workflow
Does Airwallex provide the trigger for this workflow?
No Airwallex trigger event is specified here. This workflow starts when an HTTP request reaches the Notis webhook, so an external sender must provide the payment exception and relevant phone number.
Will Dialpad place a call immediately?
The selected action creates a callback request in a Dialpad call center. It does not promise an immediate outbound call; callback handling depends on the Dialpad setup.
What if the webhook has no phone number?
The callback action needs a phone number. Include one in the webhook or have the instruction ask Notis to report the missing detail instead of creating a callback.
When this happens · Trigger
Do this · Action
Queues a callback request for an agent at a call center to handle.
Supported Triggers and Actions
Notis builds workflows that link Airwallex to Dialpad. A trigger fires from one place; an action lands in another.
Airwallex triggers
Dialpad actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Access control policies listing
Lists the company's access control policies and their permissions.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add blocked phone numbers
Blocks phone numbers from calling or texting anyone in the company.
Add department operator by id
Add an operator to a department.
Add member to channel
Add a user to a channel.
Add member to coaching team
Add a member to a coaching team.
Add operator to call center
Add an operator to a call center.
Add operator to office
Adds a user or room as an operator on an office mainline.
Add participant to call
Add someone to an ongoing call.
Connect any two apps with Notis in the middle.
Airwallex and Dialpad, or any other combination from 1,600+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Dialpad.