Set up the Customer Status Changed trigger
Add the Müşteri Durumu Değişti node and pick one group in the Durum Grubu list. The trigger fires at group level; a single status cannot be picked.
This trigger starts the flow when an operator changes a customer’s status in the panel. The choice is made per group: pick one group and every change inside it runs the flow. Pick no group and any status change starts it. Only changes made by a panel user fire the trigger; writes made by the system itself do not.
Before you start
- A finished WapCRM connection under Ayarlar > Entegrasyon; without it no group list arrives.
- A flow open in the editor; the node sits in the Tetikleyici group of the palette.
- A selection-type status group; text-type groups are shown greyed out.
- The flow switched to Aktif; an inactive flow ignores status changes.
Step by step
These screens sit inside the Intent AI section. Sign in, open Intent AI; the menu names below are in that section's left menu.
Add the node to the canvas
Drag Müşteri Durumu Değişti out of the Tetikleyici group in the Node’lar palette. It replaces the current trigger and the property panel opens on the right.
Pick the status group
Open the Durum Grubu list. Choose the group that should start the flow. If the group is missing, press Kataloğu yenile to reload the catalogue.
Read the group note and the node card
Find your group named in the note under the list; it states that any change inside that group runs the flow. The node card shows the group number too.
Result checkIf it did not work
Check these
- A WapCRM bağlantısı yok note leaves no group to pick and the flow runs on every status change. Finish the connection under Ayarlar > Entegrasyon.
- A group marked as text type cannot start automation. Choose another group of the selection type.
- This trigger has no filter for one single status. Put a Koşul node after it and test the new_customer_status variable.
Does this step look different in your panel?
We can review the screen and exact error text together.
This guide was checked against the product UI and code inventory on 29 August 2026.
