適用於聊天機器人的 Facebook Messenger 整合
關於此整合
Facebook Messenger 是我們最受歡迎的整合之一。它讓開發者能將聊天機器人直接連接到 Messenger，協助企業在最常用的社交通訊應用程式中自動化對話。
這項整合採用官方 Messenger API，確保訊息傳遞穩定、快速，並獲得 Meta 平台的完整支援。開發者只需擁有 Facebook 粉絲專頁和 API 存取權限，即可開始連接聊天機器人。
設定完成後，Messenger 機器人可以回覆問題、發送通知、處理多媒體內容，並大規模支援客戶服務。這讓 Messenger 成為企業即時溝通、貼近顧客的實用管道。
主要功能
- 自動化客戶對話
- 即時回應訊息
- 支援圖片、影片與檔案
- 根據機器人資料個人化訊息
- 大規模處理雙向訊息
- 整合 Facebook 粉絲專頁收件匣
- 根據 Messenger 事件觸發工作流程
- 提供即時客戶支援
常見問題
我要如何將聊天機器人連接到 Facebook Messenger？
要將聊天機器人連接到 Facebook Messenger，需透過 Messenger API 將 Facebook 粉絲專頁連結到你的聊天機器人平台。這需要驗證你的 Facebook 帳號並選擇要服務的粉絲專頁。
在設定 Messenger 機器人前需要準備什麼？
在設定 Messenger 機器人前，你需要一個已發佈的 Facebook 粉絲專頁、一個 Meta 開發者帳號，以及支援 Messenger 整合的聊天機器人平台。
部署 Messenger 機器人需要 Facebook 應用程式審核或核准嗎？
如果你的 Messenger 機器人要使用廣播或持久選單等進階功能，就需要通過 Facebook 應用程式審核。如果機器人僅在 24 小時內回覆用戶訊息，則不需要審核。
Messenger 機器人可以處理圖片、影片和檔案嗎？
Messenger 機器人可以收發文字、圖片、GIF、影片、語音訊息和檔案附件。
我要如何在上線前測試我的 Messenger 機器人？
在上線前，你可以讓 Facebook 粉絲專頁的管理員或編輯者與機器人進行私人對話來測試。
在 Facebook Messenger 發送訊息需要費用嗎？
在 Facebook Messenger 發送訊息不需額外費用。企業可在用戶最後互動後的 24 小時內免費發送訊息，超過這個時限則僅允許發送一次性通知或贊助訊息等經核准的訊息類型。
<iframe src="https://www.youtube.com/embed/pOIrLMpZZqc"></iframe>
The Facebook and Messenger integration empowers your chatbot to seamlessly interact across Facebook's messaging ecosystem, combining both Messenger and Facebook Page capabilities into one powerful solution. Connect your AI-powered chatbot to engage with your audience through multiple touchpoints: respond to direct messages, reply to comments on Facebook Page posts, and even initiate private conversations directly from post comments.
## Configuration (Updates)
### Manual configuration
#### Webhook Subscriptions
Using the Messenger App in your Meta app, subscribe to the following fields:
- **messages**: Required to receive incoming direct messages
- **messaging_postbacks**: Required to handle button clicks and quick replies
- **(NEW) feed**: Required to receive and respond to comments on Facebook page posts. This field is essential for the comment interaction features and proactive conversation from comments.
## Proactive Conversations
The integration now supports proactive conversation creation, letting you seamlessly move from public interactions to private DMs. When someone comments on a post from your Facebook Page, you can use that comment’s ID to automatically initiate a private conversation with the user.
## Migrating from 4.x to 5.x
### Reauthorization for comment replies
If your bot was previously connected to your Facebook page using OAuth, you will need to complete the authorization flow again in order to receive messages on the `commentReplies` channel.
### Changes to the 'Get Or Create Conversation' card
The following changes have been implemented:
- Renaming of the `id` parameter to `userId`. The ID still corresponds to the Messenger ID of the user that is or will be taking part in the conversation.
- It is now the responsibility of the Bot developer to ensure the validity of the provided user ID. No additional checks are made in the action.
### Removal of `recipientId` and `senderId` conversation tags
The `recipientId` and `senderId` conversation tags were removed because of their redundancy. The recipient ID, which corresponded to the Bot's Messenger ID, can still be found in the `recipientId` message tag of incoming messages or in the `senderId` message tag of outgoing messages. The sender ID, which corresponded to the user's Messenger ID, can still be found in the `id` conversation tag.
### Markdown message type
The Markdown message type has been deprecated, so its support has been removed in the `channel` channel. You can use the text message type to send Markdown instead.
## Migrating from 3.x to 4.x
### _postback_ and _say_ messages prefix
In version 4.0 of Messenger, _postback_ and _say_ messages no longer use the prefixes `postback:` or `say:`. If your bot relied on these prefixes for logic or transitions, you can update it to depend solely on the value set for the postback.
