最近做的企微機(jī)器人光發(fā)文字不夠——客戶咨詢產(chǎn)品要發(fā)圖文卡片帶查看詳情按鈕處理工單要發(fā)卡片帶已解決未解決按鈕讓客戶點(diǎn)。這篇重點(diǎn)講怎么用企微接口發(fā)交互卡片、怎么接收按鈕點(diǎn)擊回調(diào)、怎么處理回調(diào)后的業(yè)務(wù)邏輯。底層用的是Eyun 平臺(tái)開(kāi)放的企微 API統(tǒng)一 POSTJSON鑒權(quán)用 App Token 加 appid響應(yīng)封套{code, data, detail, message, time}code 為 0 成功。發(fā)圖文卡片sendRichText圖文卡片用消息模塊的 sendRichText 接口?？ㄆ袠?biāo)題、描述、圖片、跳轉(zhuǎn)鏈接還能帶按鈕import requests BASE https://api.eyun.com HEADERS {Authorization: Bearer eyk_xxxx, Content-Type: application/json} def send_product_card(appid, to_uin, product): card { title: product[name], description: f價(jià)格{product[price]}元\n{product[desc][:50]}, imageUrl: product[image], url: fhttps://shop.example.com/product/{product[id]}, buttons: [ {text: 查看詳情, url: fhttps://shop.example.com/product/{product[id]}}, {text: 立即咨詢, action: consult, data: {product_id: product[id]}} ] } resp requests.post( f{BASE}/wx-api/api/message/sendRichText, headersHEADERS, json{appid: appid, to: to_uin, cards: [card]} ) return resp.json()[code] 0buttons里的按鈕分兩類跳轉(zhuǎn)鏈接按鈕url和回調(diào)按鈕actiondata?；卣{(diào)按鈕點(diǎn)擊后會(huì)觸發(fā) Webhook 事件。接收按鈕回調(diào)card.action.trigger客戶點(diǎn)回調(diào)按鈕后企微通過(guò) Webhook 回調(diào)事件類型是card.action.triggerfrom flask import Flask, request app Flask(__name__) app.route(/wx-api/webhook/, methods[POST]) def webhook(): event request.headers.get(X-Eyun-Event) payload request.json[data] if event card.action.trigger: appid payload[appid] from_uin payload[fromUin] action payload[action] # 按鈕的 action 字段 data payload.get(data, {}) # 按鈕的 data 字段 handle_card_action(appid, from_uin, action, data) return okaction標(biāo)識(shí)是哪個(gè)按鈕被點(diǎn)了data是按鈕帶的業(yè)務(wù)數(shù)據(jù)如 product_id。根據(jù) action 走不同業(yè)務(wù)邏輯。處理按鈕回調(diào)按 action 分發(fā)def handle_card_action(appid, from_uin, action, data): if action consult: # 客戶點(diǎn)了立即咨詢建咨詢工單 ticket_id crm_api.create_consult( customer_uinfrom_uin, product_iddata[product_id] ) # 回發(fā)消息確認(rèn) send_text(appid, from_uin, f已為您創(chuàng)建咨詢工單 {ticket_id}客服稍后聯(lián)系) elif action resolve: # 客戶點(diǎn)了已解決關(guān)單 ticket_id data[ticket_id] crm_api.close_ticket(ticket_id) send_text(appid, from_uin, 感謝反饋工單已關(guān)閉) elif action unresolved: # 客戶點(diǎn)了未解決升級(jí) ticket_id data[ticket_id] crm_api.escalate_ticket(ticket_id) send_text(appid, from_uin, 已為您升級(jí)工單主管會(huì)盡快聯(lián)系)每個(gè) action 對(duì)應(yīng)一段業(yè)務(wù)邏輯?；卣{(diào)里的 data 是發(fā)卡片時(shí)帶的所以能知道是哪個(gè)產(chǎn)品、哪個(gè)工單。發(fā)工單卡片帶解決/未解決按鈕客服處理完工單后發(fā)卡片讓客戶確認(rèn)def send_ticket_card(appid, to_uin, ticket_id): card { title: f工單 {ticket_id} 處理完成, description: 請(qǐng)問(wèn)問(wèn)題是否已解決, buttons: [ {text: 已解決, action: resolve, data: {ticket_id: ticket_id}}, {text: 未解決, action: unresolved, data: {ticket_id: ticket_id}} ] } requests.post( f{BASE}/wx-api/api/message/sendRichText, headersHEADERS, json{appid: appid, to: to_uin, cards: [card]} )客戶點(diǎn)按鈕回調(diào)到 handle_card_action根據(jù) action 關(guān)單或升級(jí)。閉環(huán)完成?？ㄆ臓顟B(tài)更新卡片發(fā)出去后業(yè)務(wù)狀態(tài)變了工單關(guān)了卡片要不要更新企微卡片不支持動(dòng)態(tài)更新只能重新發(fā)一張新卡片舊卡片還在聊天記錄里。處理方式新卡片帶此工單已關(guān)閉提示舊卡片的按鈕點(diǎn)了也返回工單已處理不追求舊卡片更新客戶看最新的卡片就行。按鈕回調(diào)的冪等客戶可能連點(diǎn)幾下按鈕回調(diào)會(huì)觸發(fā)多次。回調(diào)處理要冪等def handle_card_action(appid, from_uin, action, data): # 用 action data 做冪等鍵 idem_key fcard_action:{action}:{data.get(ticket_id, )} if not redis.set(idem_key, 1, nxTrue, ex3600): return # 重復(fù)回調(diào)跳過(guò) # 處理業(yè)務(wù)...不做冪等客戶連點(diǎn)已解決工單被關(guān)多次雖然關(guān)多次沒(méi)副作用但其他 action 可能有。寫(xiě)在最后交互消息這套東西本質(zhì)是用好企微的卡片接口——sendRichText 發(fā)帶按鈕的卡片、Webhook 收 card.action.trigger 回調(diào)、按 action 分發(fā)處理業(yè)務(wù)邏輯。把卡片和回調(diào)串起來(lái)機(jī)器人不只是發(fā)文字還能和客戶交互。