OpenClaw Skillv1.0.1

Messenger

codedao12by codedao12
Deploy on EasyClawdfrom $14.9/mo

OpenClaw skill for Facebook Messenger Platform workflows, including messaging, webhooks, and Page inbox operations using direct HTTPS requests.

How to use this skill

OpenClaw skills run inside an OpenClaw container. EasyClawd deploys and manages yours — no server setup needed.

  1. Sign up on EasyClawd (2 minutes)
  2. Connect your Telegram bot
  3. Install Messenger from the skills panel
Get started — from $14.9/mo
5stars
1,816downloads
2installs
0comments
2versions

Latest Changelog

Expanded the Messenger skill with structured reference docs and enhanced, production-oriented guidance for Facebook Messenger Platform workflows.

- Added 7 new reference files covering API overview, messaging, webhooks, permissions, request templates, and conversation patterns.
- Updated documentation for clarity: emphasizes direct HTTPS requests, structured skill use, and operational/security best practices.
- Expanded quick orientation with specific references to new guides and workflow patterns.
- Refined required inputs and expected outputs for more robust integration planning.
- Clarified out-of-scope areas (e.g., advanced Ads/Marketing, browser OAuth).

Tags

latest: 1.0.1

Skill Documentation

---
name: messenger
description: OpenClaw skill for Facebook Messenger Platform workflows, including messaging, webhooks, and Page inbox operations using direct HTTPS requests.
---

# Facebook Messenger API Skill (Advanced)

## Purpose
Provide a production-oriented guide for Messenger Platform workflows: sending messages, handling webhooks, and managing Page messaging using direct HTTPS calls.

## Best fit
- You need bot-style messaging in Facebook Messenger.
- You want clean webhook handling and message UX.
- You prefer direct HTTP requests rather than SDKs.

## Not a fit
- You need advanced Graph API Ads or Marketing workflows.
- You must use complex browser-based OAuth flows.

## Quick orientation
- 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.

## Required inputs
- Facebook App ID and App Secret.
- Page ID and Page access token.
- Webhook URL and verify token.
- Message UX and allowed interactions.

## Expected output
- A clear messaging workflow plan, permissions checklist, and operational guardrails.

## Operational notes
- Validate signatures on all webhook events.
- Keep replies short and acknowledge quickly.
- Handle rate limits and retries with backoff.

## Security notes
- Never log tokens or app secrets.
- Use least-privilege permissions.
Security scan, version history, and community comments: view on ClawHub