# Connect OpenClaw to Facebook

Source: https://postgale.com/guides/openclaw/facebook

Yes, OpenClaw can post to Facebook Pages through Postgale. Create a Postgale API key with approval on and add https://postgale.com/mcp to OpenClaw as a remote MCP server with an Authorization header (or use a skill that calls the REST API), connect your Facebook Pages account in Postgale once, and OpenClaw can page posts, photos, video, Reels, Stories, comments and Messenger. A person can be required to approve every post, reply and message before it goes out.

## Can OpenClaw post to Facebook Pages?

Postgale is the secure layer for AI agents on social media. MCP (Model Context Protocol) is the open standard that lets AI assistants such as Claude and Cursor use outside tools. An MCP server is what they connect to. OpenClaw does not reach Facebook on its own; with Postgale connected it gets tools for the Facebook accounts you connected and nothing else.

| Task | What Postgale does |
| --- | --- |
| Publish | Text or link posts, 1 to 10 photos, video, Reels and Stories (photo or video); drafts; optional first comment. |
| Edit and delete | Change the text of a published post or delete it. |
| Comments | List comments and replies, reply, hide, delete and like. |
| Messenger | List conversations, read messages and reply (text up to 2,000 characters or an attachment) inside Meta’s 24-hour window. |
| Insights | Page views, post engagement, follows; post reach, reactions by type and clicks. |
| Meta Ads | Boost a post or create campaigns, ad sets and creatives through the connected Page. Everything is created paused and only spends with `confirm: true`. |

## What do you need?

- A Facebook Page you administer. Personal profiles cannot be connected.
- A Postgale workspace; the admin signs in with Facebook and chooses which Pages to connect.
- For photos, video, Reels and Stories: media on a public HTTPS URL (upload it with `upload_media` or bring your own).
- OpenClaw, set up as below (A remote MCP server or a skill that calls the REST API, with an API key).

## Step 1: connect your Facebook Pages account

1. Create a Postgale workspace and open Dashboard → Accounts.
2. Choose Connect Facebook Pages and sign in with the account you own, on the platform’s own page. Postgale stores the tokens encrypted and refreshes them.

## Step 2: connect OpenClaw to Postgale

1. In Postgale, open Dashboard → API keys, create a key and copy it (it starts with `sk_` and is shown once). Connect the social accounts the agent may use under Dashboard → Accounts.
2. An agent that runs on its own, on a schedule or from a chat app, should use a key with approval required: create the key, then turn on approval for it under Dashboard → API keys. Everything it wants to publish, reply or send then waits for a person.
3. Store the key where OpenClaw reads secrets, for example an environment variable `POSTGALE_API_KEY` on the machine it runs on. Do not paste it into a chat.

## Step 2a: add Postgale as an MCP server

Add a remote MCP server in OpenClaw’s configuration with these values. Field names and file locations depend on your OpenClaw version and setup; check its documentation for where MCP servers are declared.

Postgale MCP server:
```text
URL:        https://postgale.com/mcp
Transport:  Streamable HTTP
Header:     Authorization: Bearer sk_…
```

Clients that take the common `mcpServers` JSON shape accept it like this:

mcpServers entry:
```json
{
  "mcpServers": {
    "postgale": {
      "url": "https://postgale.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_…"
      }
    }
  }
}
```

## What can I ask OpenClaw to do on Facebook?

Check the connection first: “Which Facebook accounts are connected in Postgale?” Then, in plain language:

> Ask your agent: “Share our new blog post on the Facebook Page with a two-line intro, scheduled for Monday at 10am.”

> Ask your agent: “Post this video as a Facebook Reel with the caption from the brief, as a draft.”

> Ask your agent: “Draft replies to today’s Messenger messages about delivery times.”

POST /api/v1/posts (Facebook Page):
```json
{
  "content": "The fall drop is live. Shipping Thursday. Read the story behind it:",
  "platforms": [
    {
      "accountId": "acc_facebook_page",
      "platformSpecificData": {
        "link": "https://example.com/blog/fall-drop"
      }
    }
  ],
  "publishNow": true
}
```

## Which Facebook rules does Postgale enforce?

- One Postgale account per Page. After sign-in the admin picks Pages; an agent that started the connection completes the choice with `select_connection`.
- Post text up to 63,206 characters. Photo sets take 2 to 10 images.
- Reels and video Stories are uploaded by URL in Facebook’s two-phase flow; Postgale tracks processing and reports when the post is live.
- Messenger replies are allowed within 24 hours of the person’s last message (7 days with Meta’s human-agent tag); outside the window Postgale sends nothing and says why.
- Ads never spend by accident: boosts and campaigns are created paused and need an explicit confirmation to go live.

## How do I keep a person in the loop?

- Approval: tick “Hold posts from this app for approval” when you sign in, or in the Postgale dashboard require approval for the API key the agent uses (or for the whole workspace, or one account). Posts then wait as pending approval; comment replies and moderation, direct messages, WhatsApp sends and edits to live posts wait in the same queue. A person approves, edits or rejects each one in Dashboard → Approvals; the agent’s own key or sign-in cannot approve.
- Tool annotations: every Postgale tool declares whether it only reads, writes, or publishes live, deletes or spends. Clients that honour annotations ask before destructive tools run.
- Audit log: every write the agent makes is recorded with the key or the connected app, the action and the time.
- Revoking: each sign-in appears under Dashboard → Connected apps and each key under Dashboard → API keys; either can be revoked at any time.

## What can’t an agent do on Facebook through Postgale?

- Post to a personal profile or a group. Facebook’s API publishes to Pages.
- Message someone first on Messenger. Meta only allows replies to people who wrote to the Page.
- Spend on ads without a confirmation step.

## Questions

### Can OpenClaw post to Facebook Pages?

Yes, OpenClaw can post to Facebook Pages through Postgale. Create a Postgale API key with approval on and add https://postgale.com/mcp to OpenClaw as a remote MCP server with an Authorization header (or use a skill that calls the REST API), connect your Facebook Pages account in Postgale once, and OpenClaw can page posts, photos, video, Reels, Stories, comments and Messenger. A person can be required to approve every post, reply and message before it goes out.

### Does OpenClaw see my Facebook password or tokens?

No. The account owner signs in on the platform’s own page once, and Postgale stores the resulting tokens encrypted. OpenClaw only holds a Postgale API key or sign-in, which you can revoke at any time.

### Can I approve what OpenClaw sends to Facebook before it goes live?

Yes. Turn on approval for the API key it uses, the account or the whole workspace. Posts, replies and messages then wait in the Postgale dashboard until a person approves, edits or rejects them; OpenClaw’s own access cannot approve.

### Can OpenClaw schedule Facebook posts?

Yes. Ask for a date and time; Postgale stores the post as scheduled and publishes it then, and reports the result (post.published or post.failed) on your webhook and in get_post.

## Related

- [OpenClaw guide](https://postgale.com/guides/openclaw)
- [Facebook Pages for AI agents](https://postgale.com/integrations/facebook)
- [OpenClaw and Instagram](https://postgale.com/guides/openclaw/instagram)
- [OpenClaw and Threads](https://postgale.com/guides/openclaw/threads)