Triggers

An automation has exactly one trigger. It decides when the automation runs, what data the steps can read, and — for some of them — which channel the run belongs to. Triggers are grouped in the picker by source, because that is how you look for one: what happens in my inbox, on my Instagram, in my shop. The picker has a search box at the top.

​

Messages

​

Instagram

Both are locked to Instagram; the channel picker shows the lock rather than a choice.

​

Website chat

It is deliberately not the same as First message from a contact, which fires on all three channels — a rule meant to greet website visitors would otherwise greet every new WhatsApp contact too.

​

Contacts

​

Inbox

​

Forms and bookings

The three appointment triggers take an optional Appointment type filter. It lists your published booking forms and, when Cal.com is connected, your Cal.com event types, marked (Cal.com). Leave it on Any type to fire for every booking. A booking-form booking and a Cal.com booking fire the same triggers and carry their facts in the same place, so one confirmation-and-reminder automation serves both. A few values exist only for Cal.com bookings — the meeting link, the booking title, the name the booker gave and the cancellation reason. See Variables and expressions.

​

Payments

These fire on Razorpay payment links you created.

​

Online store

These fire on a connected Shopify or WooCommerce store. An automation created from the store console is tied to the store it was built for and only fires for that store’s events. One you build by hand on a store trigger is not tied to any store, and fires for every connected store.

​

Schedule

​

Triggers that do not fire yet

An automation built on one of these would save, switch on, show as active and never run. So the picker greys them out and shows why:

​

Channel scoping

Most triggers carry the channel the event arrived on, and the automation’s Channels setting narrows which of them it answers. Selecting none means every channel. Twelve triggers carry no channel at all — a form submission, a booking, a payment on Razorpay’s page, a shopper on your store website. For those the channel picker is replaced by a note saying the trigger has no channel and runs for every channel, any scope left over from a previous trigger is cleared, and the engine ignores channel scoping entirely: Form submitted · Appointment booked · Appointment cancelled · Appointment rescheduled · Payment received · Payment link expired · Payment cancelled · Cart abandoned · Order placed · Order cancelled · Order shipped · Order refunded Full detail in Channels and the 24-hour window.

​

Keyword matching

Keyword match, Instagram comment and Instagram story reply share the same keyword settings.

• Keywords is a comma-separated list. Press Enter or click away to commit the list.
• Match is either Contains the keyword (the default) or Is exactly the keyword. Exactly means the whole message is the keyword and nothing else.
• Matching is case-insensitive.

At run time, an empty keyword list means different things: Keyword match with no keywords can never match anything, while the two Instagram triggers treat keywords as an optional filter and fire on every comment or story reply. The checks panel flags an empty list on all three, and activation is refused for Keyword match. If another automation or a flow already listens for one of your words, the trigger panel shows a Keyword conflict warning. Both will fire on the same message.

​

What a trigger supplies

Each trigger puts different facts into the run, readable as tokens — the order number, the payment amount, the form answers, the booking’s start time. The insert data button beside every text field lists only the tokens that particular trigger can supply. See Variables and expressions.