A trigger is the event that starts an automation. You choose it when you create the automation: in Automations, click Create automation, then start from a library template or click Start from scratch.
This article covers each trigger, what fires it and what to check before you build your flow.
Automations do not run on the Free plan. An automation that contains a Scale plan feature (Conditions, AB Testing, API Call, etc.) can only be activated on the Scale plan or higher.
Trigger | What starts the flow | Opens the 24h window |
|---|---|---|
Inbound message | The customer sends you a WhatsApp message. | Yes |
WhatsApp Template | The customer clicks a quick reply button on a template. | Yes |
Post-purchase | An order is created on Shopify. | No |
Abandoned cart | A customer abandons their cart on Shopify. | No |
Shipment update | A Shopify shipment reaches the selected status. | No |
Incoming webhook | An external tool calls the automation URL. | No |
Store order created | Your custom store sends an order to Kanal. | No |
Store shipment update | Your custom store sends a shipment to Kanal. | No |
Recharge event | A subscription event happens in Recharge. | No |
When the trigger does not open a conversation window, the first message of the flow must be a template (Send Template action). A free-form message (Send Message) can only follow a reply or a click from the customer.
The flow starts when a customer writes to you on WhatsApp. There is a single Inbound message trigger, which replaces the former keyword triggers. You choose from 6 match modes:
Mode | The flow starts if the message... |
|---|---|
Any text | is any message, including media without text. |
Exact match | is identical to the keyword. |
Contains | contains the keyword anywhere in the text. |
Starts with | starts with the keyword. |
Ends with | ends with the keyword. |
Matches a regex | matches the regular expression you enter (advanced use). |
Case is ignored by default: "PROMO", "Promo" and "promo" are the same. Tick Case sensitive to tell upper and lower case apart.
You can add several conditions to the same trigger: the flow starts as soon as one of them is met.
To make sure customers send the right keyword, use a magic link: a link and a QR code that pre-fill the message.
Do not create an Inbound message automation on unsubscribe words (STOP, etc.). An automation keyword is checked before opt-out detection and prevents the contact from being unsubscribed. Unsubscribes are managed in Settings > Opt-out (click your team name, then Settings).
The flow starts when the customer clicks a quick reply button on a specific template. It does not start when the template is sent, nor when the customer types a free-form message.
Pick the template in the Template to send field: only templates approved by Meta are listed.
Each template button opens its own branch: the flow continues from the button that was clicked.
The automation must be active: clicks received while it is turned off are ignored.
Use this trigger to handle replies to a template sent from Klaviyo or through the API. See How to handle replies to a template sent from Klaviyo.
The flow starts when a Shopify order is created, paid or not (cash on delivery included). It does not wait for payment confirmation. In the editor, this trigger node is labeled "Order created".
It does not open a conversation window: start with a template. To handle cash on delivery orders separately, add the "Cash on delivery (COD) order" condition.
The flow starts when a customer abandons their cart on Shopify. If the customer places an order after the flow has started, the next reminders are not sent: there is no need to add a condition before each reminder.
The "Do not remind after a recent order" setting avoids reminding a customer who has just ordered (see Automation settings: re-entry and stop rules). The cart link is available with the {{variables.shopify_abandoned_checkout_url}} variable. Start with a template.
The flow starts when a Shopify shipment reaches the status selected in Event type. An automation listens to a single status: create one automation per status.
Status | When |
|---|---|
Fulfillment created | The fulfillment is created in Shopify with its tracking details. |
In transit | The package is on its way. |
Out for delivery | The package is on the delivery route. |
Delivered | The package has been delivered. |
Ready for pickup | The package is waiting for the customer at a pickup point. |
Both the tracking number and the tracking URL must be filled in on the Shopify fulfillment, for every status, including "Fulfillment created". Without them, nothing is sent.
A given shipment fires each status only once per automation.
The "delivery attempt", "failed delivery" and "returned" statuses are not available.
This trigger does not open a conversation window: use a template.
The 14 shipment variables (tracking, carrier, shipping address) are listed in Variables available in automations. See also Enable Delivery Tracking on WhatsApp.
The flow starts when an external tool (Klaviyo, Zapier, Make, your CRM) calls the automation URL. The Incoming webhook node panel shows everything you need to copy: the Destination URL, the authentication header, a JSON body example and the Copy as cURL button, which copies a complete request ready to test.
POST https://api.getkanal.com/api/v1/automations/{webhook_id}
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"phone_number": "+33612345678",
"variables": { "code": "WELCOME10" }
}The Authorization: Bearer header followed by your key is mandatory. The value is shown in the node panel. See API authentication and keys.
The body must contain phone_number. The optional variables object passes your data to the flow, usable as {{variables.name}}. The name, first_name, last_name, email and shopify_customer_id fields are also accepted at the root.
An unknown number creates a new contact.
The automation must be active, otherwise the call is rejected (error 400 "Automation is not active").
If the re-entry rule excludes the contact, the call returns 200 with "Contact blocked by re-entry rule" and no message is sent.
For Klaviyo, turn on Format JSON for Klaviyo: the body example then uses Klaviyo syntax. See Send a WhatsApp template from a Klaviyo flow.
This trigger does not open a conversation window: the first message must be a template. Technical details are in the Messaging API article.
These two triggers are for stores outside Shopify, connected to Kanal as a custom store (Settings > Stores) and fed through the Commerce API. They appear once a custom store is set up.
Store order created: the flow starts when your store sends a new order to Kanal.
Store shipment update: the flow starts when your store sends a shipment, with the same statuses as Shopify.
An order or shipment without a phone number is saved but does not trigger anything.
A shipment sends nothing without a tracking number and a tracking URL.
This trigger appears once the Recharge integration is connected, which requires the Scale plan or higher. The flow starts on one of 7 subscription events:
Subscription started
Upcoming renewal
Payment failed (on the first failure of a charge: retries do not start the flow again)
Payment permanently failed
Renewal paid
Subscription cancelled
Delivery skipped
The contact must already exist in Kanal: a Recharge event does not create a contact. See Recharge integration.
Two flows are created automatically and do not appear in the automation list. They are configured in Settings:
Opt-out: unsubscribes a contact who sends an unsubscribe keyword. See Managing unsubscribes.
Business hours: replies automatically outside your opening hours. See Set up business hours.
When a customer writes to you, Kanal starts only one automatic reply. It checks in this order:
Inbound message automations with a keyword (Exact match, Contains, Starts with, Ends with, Matches a regex).
Unsubscribe keywords (Settings > Opt-out).
Inbound message automations in "Any text" mode.
The AI Agent, if it is turned on.
The Business hours flow.
As soon as one step replies, the next ones do not run.
An active "Any text" automation replies to every message that matches no keyword. The AI Agent and the Business hours flow then no longer fire. Unsubscribe keywords still take priority.