# How to connect Facebook to Grok Bot (no API keys) > Connect Facebook to Grok Bot with ClawLink in one click — 39 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/facebook Grok Bot runs on its own cloud computer, so most Facebook guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Facebook setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Facebook actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect facebook` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Facebook. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Facebook** — `npx -y @useclawlink/cli connect facebook`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect facebook # connect Facebook (browser OAuth) npx -y @useclawlink/cli actions facebook # list available actions npx -y @useclawlink/cli run facebook --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect facebook ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Create it in Facebook for me, then confirm the important fields before you finish. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Facebook is connected in the dashboard, that agent calls the same 39 Facebook tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Facebook MCP for Grok Bot Looking for a Facebook MCP server for Grok Bot? ClawLink connects Facebook to Grok Bot and exposes 39 Facebook tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Facebook integration](https://claw-link.dev/openclaw/facebook) and the [Hermes Facebook integration](https://claw-link.dev/hermes/facebook) connect the same ClawLink account the same way. ## What the Grok Bot Facebook integration can do 39 Facebook tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 39. ### 30 of 39 Facebook tools for Grok Bot | Tool | What it does | |---|---| | **Create comment** `facebook_create_comment` | Comment on a Facebook Page post | | **Create photo post** `facebook_create_photo_post` | Create a photo post on a Facebook Page | | **Create post** `facebook_create_post` | Create a post on a Facebook Page | | **Get comments** `facebook_get_comments` | List comments on a Facebook Page post | | **Get page conversations** `facebook_get_page_conversations` | List conversations on a Facebook Page | | **Get page details** `facebook_get_page_details` | Get Facebook Page details | | **Get page insights** `facebook_get_page_insights` | Get Facebook Page insights | | **Get page posts** `facebook_get_page_posts` | List posts from a Facebook Page | | **Get post** `facebook_get_post` | Get a single Facebook Page post | | **Get post insights** `facebook_get_post_insights` | Get insights for a Facebook Page post | | **Get post reactions** `facebook_get_post_reactions` | Get reactions on a Facebook Page post | | **List managed pages** `facebook_list_managed_pages` | List Facebook Pages you manage | | **Send message** `facebook_send_message` | Send a message from a Facebook Page | | **Update post** `facebook_update_post` | Update a Facebook Page post | | **Get comment** `facebook_get_comment` | Retrieves details of a specific Facebook comment | | **Get conversation messages** `facebook_get_conversation_messages` | Retrieves messages from a specific conversation | | **Get current user** `facebook_get_current_user` | Validates the access token and retrieves the authenticated user's own profile via /me | | **Get message details** `facebook_get_message_details` | Retrieves details of a specific message sent or received by the Page | | **Get page photos** `facebook_get_page_photos` | Retrieves photos from a Facebook Page | | **Get page roles** `facebook_get_page_roles` | Retrieves a list of people and their tasks/roles on a Facebook Page | | **Get page tagged posts** `facebook_get_page_tagged_posts` | Retrieves posts where a Facebook Page is tagged or mentioned | | **Get page videos** `facebook_get_page_videos` | Retrieves videos from a Facebook Page | | **Get scheduled posts** `facebook_get_scheduled_posts` | Retrieves scheduled and unpublished posts for a Facebook Page | | **Assign page task** `facebook_assign_page_task` | Assigns tasks/roles to a business-scoped user or system user for a specific Facebook Page | | **Create photo album** `facebook_create_photo_album` | Creates a new photo album on a Facebook Page | | **Create video post** `facebook_create_video_post` | Creates a video post on a Facebook Page | | **Like post or comment** `facebook_like_post_or_comment` | Adds a LIKE reaction to a Facebook post or comment | | **Mark message seen** `facebook_mark_message_seen` | Marks a user's message as seen by the Page, visibly updating the read status in the user's | | **Publish scheduled post** `facebook_publish_scheduled_post` | Publishes a previously scheduled or unpublished Facebook post immediately | | **Reschedule post** `facebook_reschedule_post` | Changes the scheduled publish time of an unpublished Facebook post | ## Example prompts **Create Comment** > Create it in Facebook for me, then confirm the important fields before you finish. **Create Photo Post** > Create it in Facebook for me, then confirm the important fields before you finish. **Create Post** > Create it in Facebook for me, then confirm the important fields before you finish. **Get Comments** > Pull the relevant data from Facebook, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Facebook working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Facebook app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Facebook through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Facebook. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Facebook actions to the runtime in a format your agent can reliably use. | 39 tools for Facebook are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Facebook to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Facebook in the browser, and the 39 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Facebook from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Facebook tools Facebook tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Facebook call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Facebook returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Facebook and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot Facebook integration? Yes. ClawLink is the fastest way to connect Grok Bot to Facebook: link your Facebook account once in the browser and Grok Bot can call the Facebook API through 39 ready-made tools — no custom code or token handling. ### How do I connect Facebook to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect facebook` to authorize Facebook. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Facebook to Grok Bot? About two minutes. Sign in, click Connect next to Facebook in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Facebook up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Facebook working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Connect Stack Exchange](https://claw-link.dev/grokbot/stack-exchange) — Search and browse questions, answers, and developer knowledge - [Connect Zernio](https://claw-link.dev/grokbot/zernio) — Schedule social posts and pull analytics across platforms - [YouTube tools](https://claw-link.dev/grokbot/youtube) — Upload videos and manage channels