Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
OpenClaw skill for Facebook Messenger Platform workflows, including messaging, webhooks, and Page inbox operations using direct HTTPS requests.
OpenClaw skill for Facebook Messenger Platform workflows, including messaging, webhooks, and Page inbox operations using direct HTTPS requests.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Provide a production-oriented guide for Messenger Platform workflows: sending messages, handling webhooks, and managing Page messaging using direct HTTPS calls.
You need bot-style messaging in Facebook Messenger. You want clean webhook handling and message UX. You prefer direct HTTP requests rather than SDKs.
You need advanced Graph API Ads or Marketing workflows. You must use complex browser-based OAuth flows.
Read references/messenger-api-overview.md for base URLs and core object map. Read references/webhooks.md for verification and signature validation. Read references/messaging.md for Send API fields and message types. Read references/permissions-and-tokens.md for token flow and required permissions. Read references/request-templates.md for concrete HTTP payloads. Read references/conversation-patterns.md for UX flows (get started, menu, fallback). Read references/webhook-event-map.md for event types and routing.
Facebook App ID and App Secret. Page ID and Page access token. Webhook URL and verify token. Message UX and allowed interactions.
A clear messaging workflow plan, permissions checklist, and operational guardrails.
Validate signatures on all webhook events. Keep replies short and acknowledge quickly. Handle rate limits and retries with backoff.
Never log tokens or app secrets. Use least-privilege permissions.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.