Action
An action is the job a flow actually does after its trigger, condition and wait steps, such as sending a message or opening a task.
An action is what happens at the end of a flow. The trigger says what happened, the condition decides who continues, the wait step sets the timing. The action is the part that finally reaches the customer or the team. A message goes out, a task opens, a notification drops. What the customer or the team sees is usually the action.
An action should be clear and have one purpose. One flow can both send a discount coupon and alert the team if something goes wrong, but it must be obvious what each action is for. For message actions, personalising the content also shapes the result: the customer's name, product and order details separate the message from a generic announcement.
Why It Matters
- The action is where an automation means something to the customer. The other steps prepare for it.
- A well-chosen action removes small jobs the team used to do by hand.
- A clearly defined action makes it easier to measure the flow and see what works.
How It Works
- Write the job in one sentenceWhat should happen at the end of the flow? Pick one job: send a reminder, open a task or notify the team.
- Choose the channelIf the action is a message, decide which channel it goes through. Not every channel supports every action.
- Prepare the contentFor a message, write the text, the image and the buttons. Add details such as the customer name and product as variables.
- Test small firstBefore going live, send the flow to your own number or to the team and check the text and links.
Example
A new lead arrives at Liva Butik. The store owner has built a flow with two actions for this. The first sends the lead a welcome message. The second opens a task for Burak Demir to make the first call. The message includes the lead's name and the product they asked about. When Burak opens his tasks in the morning, the lead is already on the list and he starts the conversation knowing the background. Both actions come from the same event, but one faces the customer and the other faces the team.
Not to Be Confused With
An action name does not mean the same operation is supported or works the same way on every channel. An action possible on one channel may not exist on another. Check what the channel supports before choosing the action.
In Creato
In Creato, the available actions vary by channel; check the options of the channel before you build.
- In WhatsApp Marketing the actions are: standard message, carousel showcase and reminder with a coupon.
- Messages can include variables such as customer name, order number, amount and product.
- Among the ready-made scenarios in WhatsApp Marketing, the cash-on-delivery confirmation sends a message with “Confirm order” and “Cancel” buttons and writes the customer's reply into the order note.
Frequently Asked Questions
Can a flow have more than one action?
Yes. For example, one flow can message the customer and also open a task for the team. Each action still needs a clear purpose. Too many actions make a flow complicated and hard to debug. Starting with one or two actions in the first setup is safer.
How do I tell an action from a trigger?
An action is the job the flow does itself, while a trigger is the event that comes from outside. A simple rule: if a customer or the system did something, it is a trigger; if the flow does something, it is an action. An order coming in is the trigger, a thank-you message is the action. See trigger for more.
What can an action be besides a message?
In general, jobs like opening a task, notifying the team or updating a record come to mind, but these are not the same in every product. In Creato, the WhatsApp Marketing actions are message focused: standard message, carousel showcase and reminder with a coupon. Do not assume that a job missing from the list can be added to a flow; check the channel's options first.