MokoConsulting/MokoSuiteSupport
1
0
Fork 0
generated from MokoConsulting/Template-Joomla
Code Issues 11 Pull Requests Packages Projects Releases 1 Wiki Activity

Facebook Messenger channel — receive and respond to FB messages from agent dashboard #3

New Issue
Open
opened 2026-06-21 16:14:18 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-21 16:14:18 +00:00
Owner
Copy Link
Copy Source

Summary

Connect Facebook Page Messenger to the agent dashboard. Messages from Facebook appear alongside website chats in a unified inbox.

Features

  • Connect Facebook Page via Facebook Graph API / Page Access Token
  • Incoming Facebook messages appear as conversations in agent dashboard
  • Agent replies sent back to visitor via Messenger API
  • Facebook user profile photo and name displayed
  • Support for text, images, and attachments from Messenger
  • Conversation tagged with channel = 'facebook'
  • Facebook webhook verification (hub.verify_token, hub.challenge)
  • Rate limiting awareness (Facebook API limits)

Setup

  • Admin enters Facebook Page Access Token and App Secret
  • Webhook URL generated: {site}/api/mokosuitesupport/webhook/facebook
  • HMAC signature verification on incoming webhooks (X-Hub-Signature-256)
## Summary Connect Facebook Page Messenger to the agent dashboard. Messages from Facebook appear alongside website chats in a unified inbox. ## Features - Connect Facebook Page via Facebook Graph API / Page Access Token - Incoming Facebook messages appear as conversations in agent dashboard - Agent replies sent back to visitor via Messenger API - Facebook user profile photo and name displayed - Support for text, images, and attachments from Messenger - Conversation tagged with channel = 'facebook' - Facebook webhook verification (hub.verify_token, hub.challenge) - Rate limiting awareness (Facebook API limits) ## Setup - Admin enters Facebook Page Access Token and App Secret - Webhook URL generated: `{site}/api/mokosuitesupport/webhook/facebook` - HMAC signature verification on incoming webhooks (X-Hub-Signature-256)
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 html
HTML/template changes
 joomla
Joomla extension
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
Related to MokoStandards framework
 patch-release
Patch version release
 php
PHP code
 push-failure
Git push operation failed
 release-candidate
Release candidate build
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 version-drift
Version mismatch across files
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuiteSupport#3
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?