Post, schedule and run ads from Grok Bot

What is Grok Bot?

Grok Bot is a team of named agents that share one persistent cloud computer per user, so a job you start on Monday is still there on Thursday with its files, its logins and its history intact. That is a different shape from an editor or a chat window, and it is the shape marketing actually has: a campaign is a thing you come back to. Because each Bot gets a shell, Hermoso installs the same way it does on any terminal.

Grok Bot, Grok Build or Grok? xAI ships three products and says instructions for one do not transfer to the others. This page is Grok Bot. Grok Build, the terminal coding agent, has its own page, and Grok chat adds Hermoso as a custom connector at grok.com/connectors.

Hermoso is marketing on autopilot: 906+ tools over one MCP endpoint covering competitor ad research, finished image and video ads across 100+ models, publishing and scheduling to eleven social channels, and campaign management on Meta, Google Ads, Microsoft Advertising, Reddit Ads, LinkedIn, Pinterest, X Ads, TikTok Ads, Snapchat Ads, ChatGPT Ads, Apple Search Ads and AppLovin Ads. One connection, and Grok Bot has all of it.

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.

Every channel Grok Bot can publish to

Each of these has its own page with that channel’s real caption cap, its real visibility options, what it refuses and why, and a worked example phrased for Grok Bot.

Every one of them queues through one schedule_post calendar with per-channel captions, and list_scheduled reports per-channel outcomes rather than a single green tick, because “the job succeeded” and “the post went out” are different questions. A scheduled post lives in Hermoso, so it goes out on time whether or not Grok Bot is still running.

Google Business Profile is the newest channel: Posts with a photo and a button on your Google Search and Maps listing, replies to your reviews, listing edits and the calls, website clicks and direction requests the listing earns. Grok Bot reaches it through the same tools, and schedule_post queues it on the same calendar.

One channel that is built but not offered

Being straight about this is worth more than a longer list. One publishing surface exists in the codebase and is held back, waiting on the platform rather than on us:

• Reddit: organic posting and post stats are built, but Reddit’s Responsible Builder Policy requires explicit written approval before an app may use the Data API, and that ticket has not been granted. The connector is held back rather than offered as an OAuth screen leading to a dead API. Reddit Ads is a different connection and it is live: the full campaign tree, forecasting, targeting search, pixels and lead forms.

A connector that would hand you a successful OAuth and a dead API is worse than one that is not offered yet, so it is not listed as available.

Three things to type once it is connected

1. Research. “Who are my three closest competitors, and what are their longest-running Meta ads? Tell me which hook keeps repeating.” It runs find_competitors → pull_competitor_ads → mine_angles.
2. Create. “Make me a 9:16 UGC video ad using that hook, with my real product photo and captions burned in.” It runs get_brand → plan_ad → render_ad, and hands back a finished mp4 URL.
3. Ship. “Schedule it to Instagram and TikTok for Tuesday 9am, and build a paused Meta campaign around it targeting the US at $30 a day.” It runs schedule_post → create_meta_campaign → create_meta_ad.

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 yours: linking each account, once. Most channels link through the platform’s own OAuth consent screen in a browser; Bluesky takes an app password and Telegram a bot token, pasted in Hermoso. Everything after that is a tool call.

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.

What it costs

Adding Hermoso to Grok Bot costs nothing extra: there is one credit meter, and it does not care which client called. A free account starts with 30 credits at signup and 250+ more to earn. Credits are spent only on AI models and Ad Spy research; posting, scheduling, ads management and analytics are free on every channel except X, which bills per call because X charges per API request. Paid plans are $19, $49 and $149 a month for 1,000, 3,000 and 10,000 credits, and every feature is on every plan. hermoso_capabilities gives the exact credit price of any render before it runs.

Troubleshooting

• A local server prints help and exits. The arguments are missing the trailing mcp. npx -y hermoso on its own prints help; npx -y hermoso mcp starts the server.
• There is no browser on that machine. Create a key under MCP & CLI → Terminal & API keys and run npx -y hermoso auth login --token hmk_… instead.
• A channel is missing. Connect it in Hermoso under Settings → Connectors, then ask Grok Bot to run list_connectors again.
• Grok Bot answers without using Hermoso. Name it in the request: “use Hermoso to …”. That leaves no doubt about which tools should do the job.

Beyond publishing

Publishing is the last step, and it is the smallest one. The same connection gives Grok Bot the Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Reddit and Threads for research; 100+ image, video, voice and writing models on a single credit meter, with UGC avatars, dubbing, upscaling and native HTML ad formats; and the full campaign tree on twelve paid platforms. There are no per-vendor API keys to hold and no separate app to learn.

See the full tool list, every agent Hermoso works in, or what a marketing MCP is.

Hermoso in other agents

The same Hermoso account works in every agent below, so your brand, library, schedule and credits follow you between them.

Frequently asked questions

Can Grok Bot post to social media?

Yes, once you connect Hermoso's MCP server. Grok Bot can then publish to Facebook, Instagram, Threads, TikTok, YouTube, X, LinkedIn, Pinterest, Bluesky, Telegram and Google Business Profile, and schedule to all eleven from one queue with per-channel captions.

How do I add Hermoso to Grok Bot?

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. 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.

Can Grok Bot research my competitors' ads?

Yes. From Grok Bot the Meta, Google and LinkedIn ad libraries are searchable alongside organic TikTok, Instagram, YouTube, Reddit and Threads, ranked by run length, because an ad still running after months is an ad that is paying for itself. It will also tear a competitor down and return a video's voiceover, on-screen text and beat list with timestamps.

Do I need a separate account to use Hermoso in Grok Bot?

No. One Hermoso account is enough, and Grok Bot authenticates against it. The sign-in step stores the credential itself, so there is nothing to paste. The web studio at app.hermoso.ai is the same engine and the same credits.

Is it safe to let Grok Bot post and run ads for me?

Hermoso keeps the steps that cost money or cannot be undone behind gates on its own server, whatever Grok Bot is set to do: every campaign is created paused, spend switches and deletes need an explicit confirmation, and a post only reaches an account you connected and ticked in Hermoso. 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.

Does the Grok Bot template carry my Hermoso key?

No. Templates never carry secrets, so the Hermoso Marketing Bot arrives wired to Hermoso and asks for a key the first time. Create one under MCP & CLI, Terminal & API keys, and paste it into the Bot’s chat.

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.