From bde3bdae34aac50f7bd4719ae0308d4df9ac7032 Mon Sep 17 00:00:00 2001 From: sangeeta1911 Date: Sat, 4 Jul 2026 17:59:35 +0530 Subject: [PATCH 1/3] docs: rewrite Label the incoming message with real content and best practices The page was previously almost entirely a video embed that mostly covers other topics. Add an explanation of how the node actually works (it labels the contact's last incoming message), configuration steps, and the best practice of placing it right after a Wait for Response node so the label lands on the reply you actually want. Co-Authored-By: Claude Sonnet 5 --- .../07. Label the incoming message.md | 36 ++++++++++++++----- 1 file changed, 28 insertions(+), 8 deletions(-) diff --git a/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md b/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md index 1b6e71c17d..a3beab5dae 100644 --- a/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md +++ b/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md @@ -1,15 +1,35 @@ -> ### **1 minute read                                                                                                                     `Beginner`** +> ### **2 minute read                                                                                                                     `Beginner`** ___ -**Labelling the incoming message flow action is used to categorize the messages into separate buckets. This helps you capture data points which can be used for creating reports, analytics etc.** +**Labelling the incoming message flow action is used to categorize the messages into separate buckets. This helps you capture data points which can be used for creating reports, analytics etc.** -## Video Tutorial +For instance, if someone chooses English as their preferred language, you can label their message as 'English' and then generate charts for how many people chose English. - +## How it works + +This node labels the contact's most recent incoming message - not any message the bot sends. Every time the flow runs this node, it adds the label(s) you choose to whichever message the contact sent last. + +Because of this, the node only does something useful if there is a message from the contact to label at that point in the flow. + +## Adding the node to your flow + +1. Add a `Label the incoming message` node at the point in your flow where you want to categorize the contact's message. +2. Under `Select the labels to apply to the incoming message`, enter the name of an existing label or create a new one. +3. Click `Ok` to save the node. -
-
+![Add Labels node showing the label selection field](https://user-images.githubusercontent.com/32592458/218254849-f5049dcb-4c84-4250-b235-efec35a43360.png) -**For instance, if someone chooses English as their preferred language, you can label their message as 'English' and then generate charts for how many people chose English.** +## Best practices -![image](https://user-images.githubusercontent.com/32592458/218254849-f5049dcb-4c84-4250-b235-efec35a43360.png) \ No newline at end of file +- Place this node right after a `Wait for Response` node if you want to label what the contact just typed. This guarantees the incoming message being labelled is the reply you're interested in, not an older message from earlier in the conversation. +- If you add this node without a `Wait for Response` immediately before it (for example, right at the start of a flow, before the contact has said anything), there is no incoming message yet and the label is not applied to anything. +- You can add more than one label to the same node. If the same message already has a label from an earlier point in the flow, the new label is added alongside it rather than replacing it. +- Keep label names consistent across flows (for example, always use `English` rather than mixing `english` and `English`) so your reports and BigQuery analytics can group them correctly. + +--- + +## Related video + +This video walks through building a full flow and includes an example of using the `Label the incoming message` node partway through - it's a good reference for seeing the node used in context, but isn't focused on this node alone. + + From 906d9f78920d2346d32a406749abac26030933cf Mon Sep 17 00:00:00 2001 From: Sangeet Mishra <143380171+SangeetaMishr@users.noreply.github.com> Date: Sat, 4 Jul 2026 18:04:14 +0530 Subject: [PATCH 2/3] Update 07. Label the incoming message.md --- .../2. Flow Actions/07. Label the incoming message.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md b/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md index a3beab5dae..a0c61ef5ca 100644 --- a/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md +++ b/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md @@ -1,4 +1,13 @@ -> ### **2 minute read                                                                                                                     `Beginner`** +

+ + + + + + +
3 minutes readLevel: Beginner Last Updated: July 2026
+

+ ___ **Labelling the incoming message flow action is used to categorize the messages into separate buckets. This helps you capture data points which can be used for creating reports, analytics etc.** From ae40576980cbaf570d1d352c9be7eb9458da88ba Mon Sep 17 00:00:00 2001 From: sangeeta1911 Date: Sat, 4 Jul 2026 18:28:45 +0530 Subject: [PATCH 3/3] docs: remove leftover horizontal rule under the page header Co-Authored-By: Claude Sonnet 5 --- .../03. Flows/2. Flow Actions/07. Label the incoming message.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md b/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md index a0c61ef5ca..56d7a42d98 100644 --- a/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md +++ b/docs/4. Product Features/03. Flows/2. Flow Actions/07. Label the incoming message.md @@ -8,8 +8,6 @@ -___ - **Labelling the incoming message flow action is used to categorize the messages into separate buckets. This helps you capture data points which can be used for creating reports, analytics etc.** For instance, if someone chooses English as their preferred language, you can label their message as 'English' and then generate charts for how many people chose English.