Neura Market Logo

Messenger

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

codedao12

@codedao12

What This Skill Does

Provides direct HTTPS-based workflows for Facebook Messenger Platform, covering message sending, webhook handling, and Page inbox operations. Includes reference guides for API endpoints, token management, and conversation UX patterns.

Replaces reliance on Facebook SDKs by offering a lightweight, direct HTTP approach to Messenger API operations with clear security and rate-limit guidance.

When to Use It

  • Send a text or template message to a Messenger user via the Send API
  • Verify and validate incoming webhook events from Facebook
  • Set up a persistent menu and get-started button for a Page
  • Handle message delivery receipts and read receipts in webhooks
  • Manage Page inbox conversations with quick replies and typing indicators
  • Retrieve and refresh Page access tokens for automated messaging

Install

$ openclaw skills install @codedao12/messenger

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.

Top skills in this category

Telegram

@codedao12

OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).

2921k

Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Google My Business, TikTok, Pinterest, Dribbble, Discord, Slack, Kick, Twitch, Mastodon, Bluesky, Lemmy, Farcaster, Telegram, Nostr, VK, Medium, Dev.to, Hashnode, WordPress, ListMonk

@nevo-david

Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Goog...

3413k

google-meet

@byungkyu

Google Meet API integration with managed OAuth. Create meeting spaces, list conference records, and manage meeting participants. Use this skill when users want to interact with Google Meet. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Meet connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Meet action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Meet examples; they add no Google Meet capability - Google Meet is not an event source, a trigger cannot read Google Meet data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

1519k

Facebook

@hith3sh

Manage Facebook Pages, posts, comments, messages, and insights via the Facebook Graph API. Use this skill when users want to post content, read engagement metrics, moderate comments, or automate Facebook Page workflows from chat.

337.8k

Google Meet

@hith3sh

Google Meet API integration with managed OAuth. Create meeting spaces, inspect conference records, retrieve recordings and transcripts, and manage meeting pa...

327.2k