The step that handles tags, fields, assignment, status, sequences and comment moderation: the thirteen action kinds, why order matters, how handover ends the flow, and what the check looks at.
A flow does not only send messages; behind the scenes it tags people, records what they said, and assigns the conversation to a colleague. The Action step is where all of that happens. This guide covers the step's place in a flow, the thirteen action kinds, why the order matters, and what the pre-publish check looks at here.
π‘ The field-by-field setup of every action is covered in How the Action step works and in the articles split by subject. This article is about the step's behaviour inside the flow.
What it does
The Action step sends nothing to the person (with one near-exception: a team notification appears in the panel and never reaches the customer). Its work stays on the contact card, in the conversation, or on the comment under a post.
One step can hold several actions β at most 20. They are applied top to bottom, in order.
The step works on both channels; only the comment actions are Instagram-specific.
Write to a field β writes a value into a contact field (placeholders allowed).
Increase/decrease a field β raises or lowers the number in a field. A value that cannot be read as a number counts as 0, so the first increase on an empty field gives 1.
Hide the comment β hides the comment that started the flow, or unhides it. It is reversible: the comment stays visible to its author.
Delete the comment β deletes it from Instagram permanently. It is irreversible and cannot be published without ticking the confirmation box.
Why order matters
Actions are applied in the order you wrote them, and that order changes the outcome.
Two typical examples:
Writing Remove tag (new) first and Add tag (customer) second moves the contact into the right state. In the reverse order you get the same result β but if you both add and remove the same tag, the last one wins.
Actions after Hand over to a human are still applied (the handover is evaluated at the end of the list), but the steps after this one do not run: the session ends there.
Handover ends the flow
This is the step's most important behaviour. If the list contains a Hand over to a human action, the flow does not continue from Next once the step finishes; the session closes with the reason "handed over".
So anything that has to happen after the handover (tagging, writing a field) must go inside the same step. Put it in the next step and it will never run.
Its output
The step has one output, Next β unless there is a handover. Even if one of the actions fails, the flow continues; the reason is written line by line to the run log.
Special rules for comment actions
Hiding and deleting comments differ from the other actions in three ways:
They only work on Instagram. With WhatsApp connected the check warns you, and at run time the step is skipped.
They need comment context. If the flow did not start from a comment the action is skipped and the log records "no comment".
At most 2 comment moderations are applied per run. The limit exists so a flow that falls into a "wait β hide" loop cannot hide and unhide the same comment over and over, and it still holds on the turn after a wait.
Deletion is protected further: without the I understand the comment will be deleted permanently box ticked, the flow cannot be published and nothing is deleted at run time. This stops a deletion copied from a template from quietly reaching live.
β οΈ Note: Deleting a comment also loses your right to send a private reply from it. If a flow both deletes and sends, the check warns you: the message may run into the 24-hour window and never go out.
What the pre-publish check looks at here
Add an action (error) β the list is empty.
An action is incomplete (error) β a tag name, field or notification text was left blank.
Comment deletion was not confirmed (error) β the confirmation box is not ticked.
This flow has no comment trigger (warning) β the comment action will always be skipped.
Comment reply only works on Instagram (warning) β on an account with WhatsApp, the comment action is skipped.
The flow both deletes the comment and sends a message (warning) β the conflict described above.
An example
A consultancy wants to route people asking about prices to the sales team.
They add the keyword price to the Start step.
Message: "Our pricing depends on your needs. A colleague will write shortly π"
They add an Action step with four actions in order:
Add tag β asked-price
Write to a field β last_request = {{input}}
Notify the team β "Price request: {{contact.name}}"
Hand over to a human β a member of the sales team
They leave the step unconnected; the handover already ends the flow.
The result: the person gets an answer, the team sees a notification, the conversation opens for the right person, and the text of the request sits on the contact card.
Common mistakes
Putting tagging in the step after a handover. The handover ends the flow; that step never runs. Add the tag to the same action list.
Thinking the team notification reaches the customer. It does not; it only appears in the panel. To say something to the customer use The Message step.
Putting a comment action in a keyword-started flow. There is no comment context, so it is skipped every time.
Leaving the deletion confirmation for later. The flow cannot be published.
Adding and removing the same tag in one step. The last one wins, which is probably not what you meant.
Piling twenty actions into one step. It works technically but reads terribly. Split the work by meaning.
Using increase/decrease on a text field. A value that cannot be read as a number counts as 0, and the text in the field is lost.
Limits
At most 20 actions in a step; they are applied in order.
Comment actions work on Instagram only, only in flows started from a comment; at most 2 comment moderations per run.
Delete the comment is irreversible and requires confirmation.
Hand over to a human ends the flow.
Notification text at most 300 characters; a field value at most 500; a tag name at most 60.
One output: Next (when there is no handover).
Every action kind is its own plan feature; with one out of scope, the run stops at the step.
Related concepts
The concept itself is covered in What is an action. How the same actions are used outside automations, in general rules, is explained in What is a general rule. If an action is not working, My action is not working lists the causes starting from the run log.
Messages carry the conversation; actions leave behind the useful part of it.