← العودة
Blog Post
عنوان المحادثة: Done. Here's what changed:Buttons restored: Reverted bot reply to Meta...
التاريخ: 11.04.2026
التصنيف: 🧠 الذكاء الاصطناعي وتعلم الآلة
إجمالي الرسائل: 5 | ياسر: 5 | M: 0
Yasser
Done. Here's what changed:Buttons restored: Reverted bot reply to Meta API — interactive buttons (reply buttons, list messages) work again. bot-prepare-send.js now builds Meta API data with phone_number_id, buttons, listMessage.ManyChat ai_reply field still synced: The Respond OK node pulls mcResponse from Prepare Send (with set_field_value action only, no messages) so ManyChat tracks the AI response.About the number issue: Both bot replies AND accountant notifications still send from the old number (+962 7 8265 6317) because we don't have the phone_number_id for the new number (+962 7 8545 3379). The new number's WABA was created through ManyChat's Embedded Signup and our Meta token doesn't have access to it.To fix the number issue, I need one of:The phone_number_id for +962785453379 — find it in ManyChat > Settings > WhatsApp Channel or Meta Business Suite > WhatsApp ManagerA ManyChat API token — from ManyChat > Settings > APIWith either of these, I can switch everything to send from the correct number while keeping buttons.
Yasser
All changes deployed. Here's what was implemented:Hybrid sending architecture — correct number for customers, buttons for team:Main bot reply → ManyChat Dynamic Block (sends from +962785453379, text-based)Customer reports → ManyChat API sendContent when manychat_id available (correct number); falls back to Meta API for list messages/buttonsCustomer notifications (payment confirmed, etc.) → ManyChat API sendContent (correct number) when the notification phone matches the webhook senderTeam notifications → Meta API (old number +962782656317) with interactive buttons preservedFiles modified:bot-format-report.js — added manychat_id to all 3 return objectsbot-send-report.js — added ManyChat API attempt before Meta API fallbackbuild.js — MC_TOKEN constant, smartSendWACode with ManyChat attempt, Prepare Notifications passes manychat_id for customer notifs, notification workflow Prepare Query/Recipients carry manychat_id throughThe customer should now receive all messages from the new number. Team members keep their interactive buttons from the old number.
Yasser
// TODO: Replace WA_TOKEN with a System User Access Token that has whatsapp_business_messaging permission on WABA 993987600475107
Yasser
التوكن الحالي (EAAPv6K...) لا يملك صلاحية الإرسال من الرقم 1909445923039673 لأنه على WABA مختلف. تحتاج توفير System User Access Token لـ WABA 993987600475107 يملك صلاحية whatsapp_business_messaging. بعد ذلك:
المحادثة الكاملة - 11.04.2026
ياسر
Done. Here's what changed:Buttons restored: Reverted bot reply to Meta API — interactive buttons (reply buttons, list messages) work again. bot-prepare-send.js now builds Meta API data with phone_number_id, buttons, listMessage.ManyChat ai_reply field still synced: The Respond OK node pulls mcResponse from Prepare Send (with set_field_value action only, no messages) so ManyChat tracks the AI response.About the number issue: Both bot replies AND accountant notifications still send from the old number (+962 7 8265 6317) because we don't have the phone_number_id for the new number (+962 7 8545 3379). The new number's WABA was created through ManyChat's Embedded Signup and our Meta token doesn't have access to it.To fix the number issue, I need one of:The phone_number_id for +962785453379 — find it in ManyChat > Settings > WhatsApp Channel or Meta Business Suite > WhatsApp ManagerA ManyChat API token — from ManyChat > Settings > APIWith either of these, I can switch everything to send from the correct number while keeping buttons.
11.04.2026 19:41
ياسر
All changes deployed. Here's what was implemented:Hybrid sending architecture — correct number for customers, buttons for team:Main bot reply → ManyChat Dynamic Block (sends from +962785453379, text-based)Customer reports → ManyChat API sendContent when manychat_id available (correct number); falls back to Meta API for list messages/buttonsCustomer notifications (payment confirmed, etc.) → ManyChat API sendContent (correct number) when the notification phone matches the webhook senderTeam notifications → Meta API (old number +962782656317) with interactive buttons preservedFiles modified:bot-format-report.js — added manychat_id to all 3 return objectsbot-send-report.js — added ManyChat API attempt before Meta API fallbackbuild.js — MC_TOKEN constant, smartSendWACode with ManyChat attempt, Prepare Notifications passes manychat_id for customer notifs, notification workflow Prepare Query/Recipients carry manychat_id throughThe customer should now receive all messages from the new number. Team members keep their interactive buttons from the old number.
11.04.2026 20:22
ياسر
n8n_workflows
11.04.2026 21:26
ياسر
// TODO: Replace WA_TOKEN with a System User Access Token that has whatsapp_business_messaging permission on WABA 993987600475107
11.04.2026 22:28
ياسر
التوكن الحالي (EAAPv6K...) لا يملك صلاحية الإرسال من الرقم 1909445923039673 لأنه على WABA مختلف. تحتاج توفير System User Access Token لـ WABA 993987600475107 يملك صلاحية whatsapp_business_messaging. بعد ذلك:
11.04.2026 22:28