Post to Facebook from Grok Bot

A Bot that keeps running is a good match for the one channel with a real draft state: it can research, render and stage all week, and you approve a queue rather than a stream of interruptions.

Hermoso is a marketing MCP server: 906+ tools over one OAuth’d endpoint that let an agent research the ads already running in a market, generate finished image and video ads, publish them, and build the paid campaigns behind them. Grok Bot reaches all of it through one connection. This page covers one slice of that: what Grok Bot can actually do on Facebook, and what Facebook will not let it do.

Connect Hermoso to Grok Bot

  1. Fastest: add the Hermoso Marketing Bot template. Open the template and add it to Grok Bot. It arrives wired to Hermoso but with no key, because templates never carry secrets, so it asks for one: create a key under MCP & CLI → Terminal & API keys and paste it into the Bot’s chat. A key carries real spend authority, so treat it like a password.
  2. Or sign in from the Bot’s own terminal. Every Bot gets a browser, a filesystem and a shell, so the keyless install works there too:
    npm install -g hermoso && hermoso auth login
    The hermoso command is then available to the Bot with nothing pasted into a config file. Settings → Plugins is a catalog of pre-built connectors that does not list Hermoso, so the template and the terminal are the ways in today.
  3. Using Grok Build instead? xAI’s terminal coding agent is a separate product with its own setup: see Hermoso in Grok Build.
  4. Ask a Bot for something. “Pull my three closest competitors’ longest-running ads and remix the best hook into a 9:16 video,” or “post this render to the channel.” The agent picks the tools; you approve the spend.

Hermoso is not affiliated with or endorsed by xAI and does not claim to be. The Hermoso Marketing Bot template is published by Hermoso; the same steps are in the app under MCP & CLI, on the Grok Bot tab of the agent setup.

Then connect Facebook itself, once, under Settings → Connectors in Hermoso. That is an OAuth consent screen, so it is the one step that needs a browser. Everything after it is a tool call.

The Facebook tools Grok Bot gets

  • post_to_meta: publishes text, an image, a video or a multi-photo post to the Page, and takes pageId so it never has to guess which Page.
  • schedule_post: queues the same post for a time you choose, on one calendar shared with every other channel.
  • list_meta_pages: lists the Pages the account has connected, with their ids.
  • manage_meta_post: edits the copy of a published post, or deletes it.
  • list_meta_comments / reply_to_meta_comment / moderate_meta_comment: reads the comments under a post, replies as the Page, and hides or deletes what should not be there.
  • meta_page_insights / meta_post_insights: Page-level and per-post reach, impressions and engagement.
  • upload_meta_asset: puts a finished render into the ad account’s asset library.

Facebook is also the one channel with native remote scheduling. post_to_meta takes a scheduleAt between ten minutes and thirty days out and hands the timing to Meta itself. Instagram and Threads have no such thing in Meta’s API, and passing it for them is refused rather than quietly posted immediately.

Facebook limits worth knowing before you automate anything

TextA Facebook post can run to 63,206 characters, which is effectively no limit. It is enforced when the post is created or queued, so an overlong post is refused while you are still there to fix it instead of being silently cut on the way out.
VisibilityPublic or draft. A draft is a genuinely unpublished Page post, which is the useful one for review: it exists in Meta Business Suite and nobody outside can see it. There is no unlisted and no private option: “a Facebook Page post is either published or held as an unpublished draft”.
Carousel2 slides and up, photos only. Meta publishes no maximum for attached_media that we could source, so Hermoso does not invent one and attribute it to Facebook. The only bound is ours, at 30 slides, and the refusal says whose it is: “Facebook publishes no documented maximum for attached_media, so this bound is ours, not theirs.” Video cannot ride in a Facebook photo carousel; that is a different edge on Meta’s API and Hermoso refuses rather than silently dropping the clip.
Which accountpageId. It matters the moment a brand connects more than one Page: the publish path refuses by name instead of picking one for you, and a schedule that could not carry the answer would turn that refusal into a failure hours later with nobody watching.

Try it in Grok Bot

Ask for it in ordinary language. These are plain sentences, not a DSL:

“Every weekday morning, check what my three competitors ran yesterday, and if anything is new, remix the strongest hook into a 4:5 image ad and leave it on my Page as a draft.”

That walks find_competitors → search_meta_ads → plan_ad → render_ad → list_meta_pages → post_to_meta. Approval is Grok Bot’s setting rather than ours, and the shared machine is the reason to think about it: isolation is per user, not per Bot, so anything one Bot connects, every Bot on that machine can reach.

Grok Bot on Facebook: the part that bites

Facebook is where the persistent machine pays off, because the draft is genuine: the post exists in Business Suite, nobody outside can see it, and a published one can still be edited or deleted afterwards. Pin the pageId in the job rather than letting each run resolve it. With more than one connected Page the publish path refuses to guess, which is correct and which a Bot working at 6am cannot answer.

For a long unattended run the hermoso CLI is the cheaper path: the agent shells out per command instead of carrying an 906+ tool manifest through every turn of a job that might run for days.

Research Facebook before you post

The Meta Ad Library is the richest public creative archive there is, and search_meta_ads reads it by keyword or by page, covering both Facebook and Instagram placements. pull_competitor_ads and competitor_teardown build on it, and find_competitors works out who to point them at.

The paid half

Facebook is the deepest paid surface Hermoso has. create_meta_campaign, create_meta_adset and create_meta_ad build the whole tree with real targeting: geography down to a city radius, interests, behaviours, custom audiences and lookalikes, placements, dayparting, bid and cost caps. Everything is created PAUSED with no caller override, and the summary your agent reports is built from a read-back of what Meta actually stored, never from what was requested. Before a budget is committed, preview_meta_ad renders the real ad per placement as a link you can look at and estimate_meta_reach says how many people the targeting actually reaches. One warning that saves money: an ad set created with no locations defaults to the United States only, and the read-back says so loudly.

What Grok Bot cannot do on its own

An agent with a budget is only useful if the blast radius is bounded, so the fence is in the server rather than in a prompt. Every ad campaign, ad set, ad group and ad is created paused, and the status switches that arm real money refuse to run without an explicit confirmation flag. Every render is quoted first (hermoso_capabilities publishes each model’s exact credit cost before anything spends). Credits are reserved before the first provider call and settled at the exact cost afterwards, so a failed dispatch refunds rather than leaving you billed for nothing. Deletes are confirm-gated too, and every campaign tree is read back from the ad platform before your agent tells you what it built.

One step is deliberately not headless: linking an account is an OAuth consent screen, so you connect the channel once in a browser. Everything after that is a tool call.

The rest of the matrix

From Grok Bot, post to: Instagram · Threads · TikTok · YouTube · X · LinkedIn · Pinterest · Bluesky · Telegram. Or see everything Grok Bot can publish to.

Post to Facebook from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Hermes · Gemini CLI · Perplexity · Le Chat · Claude Cowork · Perplexity Computer · Paperclip

Frequently asked questions

Can Grok Bot post to Facebook?

Yes, through Hermoso's MCP server. Add the Hermoso Marketing Bot template from x.ai/bot/THQqogUKuhn1whWU0hrmb, which arrives wired to Hermoso and asks for an API key you create under MCP & CLI, Terminal & API keys. Or run npm install -g hermoso && hermoso auth login in the Bot's own terminal, which stores the credential with nothing pasted. Grok Bot then has 906+ tools, including the ones that publish to Facebook, plus the ones that research the ads already running in your market and render the creative in the first place.

How do I connect Facebook to Grok Bot?

Two steps, once each. Add the Hermoso Marketing Bot template from x.ai/bot/THQqogUKuhn1whWU0hrmb, which arrives wired to Hermoso and asks for an API key you create under MCP & CLI, Terminal & API keys. Or run npm install -g hermoso && hermoso auth login in the Bot's own terminal, which stores the credential with nothing pasted. Then connect Facebook inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Grok Bot publishes to Facebook as an ordinary tool call.

Does Grok Bot need my Facebook password?

No. You connect Facebook to Hermoso once through an OAuth consent screen in a browser, and Grok Bot then reaches it as a tool call. Linking an account is the one step that is not headless; nothing after it needs a password, and no credential is ever handed to the model.

Can Grok Bot research Facebook before it posts?

Yes. The Meta Ad Library is searchable through search_meta_ads by keyword or by page, and it covers Facebook and Instagram placements together.

Can Grok Bot post a carousel to Facebook?

Yes, as a Facebook multi-photo post: two slides and up, photos only. Meta publishes no maximum for it that we could source, so Hermoso applies its own bound of 30 slides and says the bound is ours rather than attributing it to Facebook. Grok Bot calls the same publish tool either way, and a channel that cannot carry a carousel is refused with the real reason attached.

Can Grok Bot run Facebook ads as well as posting?

Yes. The full Meta campaign tree is buildable (campaign, ad set, ad, targeting, audiences, budgets), with preview and reach-estimate tools before a budget is committed.

Related

The long version, with the setup and what it did in practice: run your marketing with a Grok bot and autonomous marketing with a Grok bot.

The same bot on other channels: X, Instagram, TikTok, YouTube, LinkedIn, Threads and Pinterest.

Start free with 30 credits at signup and 250+ more to earn. Every feature is on every plan. Credits are spent only on AI models and Ad Spy research; posting, scheduling, ads management and analytics are free.

Start free →   See pricing