Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(examples): read chatId from the Set node in the booking flow

Yudhi Armyndharis6be43f356431
diff --git a/docs/examples/n8n-appointment-booking.md b/docs/examples/n8n-appointment-booking.md
index 75a06a164..532eda7fc 100644
--- a/docs/examples/n8n-appointment-booking.md
+++ b/docs/examples/n8n-appointment-booking.md
@@ -59,7 +59,7 @@ For a production workflow, replace this with a classifier, a structured form flo
## Normalize the Request
-Add a **Set** node to extract the values your booking system expects.
+Add a **Set** node named `Normalize request` to extract the values your booking system expects.
Suggested fields:
@@ -97,12 +97,14 @@ The availability step should return whether the requested slot is available and,
When the requested slot is available, create the booking in your scheduling source and send a confirmation with the **OpenWA: Send Text** node.
-| Field | Value |
-| --------- | -------------------- |
-| Resource | Message |
-| Operation | Send Text |
-| Chat ID | `{{$json.chatId}}` |
-| Text | Confirmation message |
+| Field | Value |
+| --------- | ----------------------------------------------- |
+| Resource | Message |
+| Operation | Send Text |
+| Chat ID | `{{ $('Normalize request').item.json.chatId }}` |
+| Text | Confirmation message |
+
+Each node replaces `$json` with its own output, so after **Create Booking** `$json` holds the booking system's response, not `chatId`. Read fields from the trigger or the Set node by name through `$('<node name>').item.json`.
Example confirmation text:
@@ -114,7 +116,7 @@ Reply CANCEL if you need to cancel or change it.
## Alternative Slots Message
-When the requested slot is not available, send available alternatives instead of failing silently.
+When the requested slot is not available, send available alternatives instead of failing silently. Use the same Chat ID expression, `{{ $('Normalize request').item.json.chatId }}`, on this **OpenWA: Send Text** node.
Example text: