How to connect Grok Bot to Instagram: the plugins that post, and the route that breaks Instagram's terms

Grok Bot can post to Instagram, but not through anything xAI or Meta built for it. xAI's documentation never mentions Instagram, and the Cursor Marketplace, where Grok Bot gets its plugins, has no Instagram or Meta plugin. What works is a scheduling tool's plugin, Postiz or Buffer, or Composio's connection to Meta's own API, each publishing to an Instagram professional account. The other way, letting the Bot sign in to instagram.com and click Post itself, runs straight into Instagram's terms.

Below is how each route works, what Grok Bot costs, what Meta's API will and will not publish, and how to set the Bot up so it drafts your week and waits for you instead of posting on its own. Everything is checked against xAI's, Cursor's and Meta's own pages, photographed on 14 October 2026.

Which way should you connect Grok Bot to Instagram?

What is Grok Bot?

Grok Bot is xAI's agent product: named AI teammates you message like a colleague, each working on a cloud computer with a browser, files and a terminal, so the work carries on when your laptop is shut. It launched in beta on 11 August 2026. xAI's announcement says:

Grok Bot is in beta and available today for SuperGrok, SuperGrok Plus, and SuperGrok Heavy; Cursor Pro, Pro+, and Ultra; and Cursor Teams Standard and Premium subscribers on desktop and iOS.

The docs add Windows, Linux and Android since then, and X Premium+ can now be linked too. Two parts of it matter for Instagram. Bots install plugins for apps that have them and use the browser for everything else. And a Bot can save a job as a skill and run it on a schedule as a routine, which is what turns "make me a post" into "have this week's posts ready every Monday".

How much does Grok Bot cost?

There is no separate Grok Bot price. It is included with SuperGrok, SuperGrok Plus and SuperGrok Heavy, with X Premium+, and with Cursor Pro, Pro+, Ultra and Teams, each with its own weekly allowance. Cursor's help page, which is where the usage is metered, lists the one plan that does not qualify:

The usage is separate from your Grok chat usage and resets every week. When it runs out, extra usage is billed through Cursor if on-demand billing is on. A new account gets a trial credit that Cursor says can be used up by a single long job, so try it on one post, not on a month of them.

Is there an official Instagram plugin for Grok Bot?

No. Grok Bot has no plugin list of its own. Its documentation for teams says it "inherits your team's Cursor connector policy. There is no separate Grok Bot connector list, and connectors appear as plugins in the app." So the catalogue that matters is the Cursor Marketplace, and the Instagram page there does not exist:

Meta does publish MCP servers, three of them, for ads, for developer apps and for WhatsApp, and none posts to an Instagram feed, as we found when we connected ChatGPT to Instagram. So every working route to an Instagram post from Grok Bot goes through someone else's software. That is not a reason to avoid it. It is a reason to know whose.

Route 1: the Postiz plugin

Postiz is an open source scheduler, and of the eight vendors we read it has the clearest Grok Bot setup. Its plugin is on the Cursor Marketplace, and the listing names Instagram among the platforms it reaches:

• Make a Postiz account and connect your Instagram professional account inside Postiz. That connection is between Postiz and Meta, not Grok Bot.
• Create a Postiz API key.
• In a Bot chat, type /add-plugin postiz, or add it from Connect apps.
• Store the key as a secret when the Bot asks. Postiz's page calls it POSTIZ_API_KEY. Use the masked secret card, never the chat.
• Ask for a post: a feed post, a Story or a Reel, with the image or video, the caption and a time.

One sentence on Postiz's page is more confident than xAI's: it says Bots "ask before changing external systems". xAI's documentation does not promise that for publishing. It tells you to ask for it, which is the section on safety below.

Route 2: the Buffer plugin

Buffer's plugin is marked on the marketplace as created and verified by Cursor itself. Its description is general: draft, schedule and publish posts across the channels you have connected in Buffer.

So whether it reaches Instagram is a question about your Buffer account, not about Grok Bot. If your Instagram is already connected in Buffer and you already plan posts there, this is the least new software to trust: one plugin, the queue you already know, and Buffer's own limits. Install it with /add-plugin buffer.

Route 3: Composio and Meta's API

Composio is a connection layer for agents, and its Grok Bot plugin is listed on x.ai itself, published through the Cursor Marketplace. Its Instagram tools map one to one onto Meta's Instagram API: create a media container, create a carousel container, publish, check the publishing limit. You sign in to Instagram through Composio's consent screen rather than handing over a key.

Composio's page describes single photos, videos and carousels on Instagram Business and Creator accounts. It does not describe Stories or scheduling, so if you want a post to go out on Thursday at 9, you need either a Grok Bot routine that publishes at 9 or one of the schedulers above. We covered Composio's plans in our Claude version of this guide.

Can Grok Bot just log in to Instagram and post?

Technically, yes, and xAI presents this as the point of the product:

They can sign in and work across apps, tools, and websites, including platforms with no clean API or MCP, and come back with the work finished.

Instagram is not one of those platforms. It has an API for exactly this job, and its terms rule out the alternative. Section 4.2 of Instagram's Terms of Use says you cannot access the service "in an automated way without our express permission, regardless of whether such automated access or collection is undertaken while logged-in to an Instagram account":

There is a practical risk on top of the rule. xAI's security documentation says the hosted computers "use shared static egress by default", so unless you route the Bot through your own desktop, your Instagram login arrives from a shared cloud address rather than from your phone or your office. And xAI itself says a site can refuse:

Where the browser route is fine is reading your own public profile, or checking that a post went out. For publishing, use one of the three plugins. Scraping is a separate question we answered in is scraping social media legal.

What will Instagram accept from Grok Bot?

Whichever plugin you choose, the post reaches Instagram through Meta's Content Publishing API, so Meta's rules are the ceiling. The ones that matter:

• Professional accounts only. Business or Creator. A personal account cannot be published to through the API.
• JPEG images on a public URL. Carousels of up to 10 items, Reels, and Stories are all supported.
• No scheduling in the API itself. The schedule lives in Postiz, Buffer or your Bot's routine.
• 100 posts in any 24 hours, carousels counting as one.

Instagram accounts are limited to 100 API-published posts within a 24-hour moving period. Carousels count as a single post.

One more line on Meta's page, and no vendor guide we read mentions it. If Grok made the picture, the API lets you say so:

Ask your plugin whether it passes is_ai_generated. If a Bot made the image, Instagram may label it anyway, for the reasons in why Instagram says AI info on your post.

How do you stop Grok Bot posting without asking?

Tell it to stop before publishing, in writing, every time it matters. xAI's documentation does not list publishing among things that wait for you by default. It lists it among things you should make wait:

Keep sending, publishing, purchasing, deletion, and production changes behind approval.

When a Bot does stop, you get a card with Allow once, Always allow and Deny. Behind those cards is Auto Review, a separate model that checks risky actions, which xAI says complements explicit boundaries rather than replacing them. Two details catch people out. Always allow saves a rule, so one tap can turn every future post into an unreviewed one. And an approval requested by a routine running while you are away expires after about ten minutes, and the action does not run.

Secrets need the same care. All your Bots share one computer, its browser sessions and its files, so a key one Bot can use, every Bot can use. Store plugin keys through the masked secret request, which the Bot sees only as [REDACTED], and never paste a key or password into the chat, whatever a vendor's setup guide says.

A routine that drafts your week and waits for you

The useful version of Grok Bot for Instagram is not a Bot that posts. It is one that has a week of posts ready for you to look at on Monday morning. xAI describes the building blocks like this:

Do the job once with the Bot, save it as a skill, then schedule it. A request in the shape of xAI's own examples, written for a small business, would read like this. We have not run it; treat it as a starting point and test it on one post first.

Every Sunday at 6pm, run the Weekly Instagram skill: read this week's offers from our website and the notes in /workspace/brand, draft four Instagram posts in Postiz for Monday, Wednesday, Friday and Saturday at 9am, each with its image, caption and alt text, and leave them as drafts. Do not publish or schedule anything. Post the four drafts in this conversation for my approval. If our website is unreachable, tell me instead of using last week's offers.

Two things a routine like this cannot do for you. It cannot know an offer has ended unless the source it reads says so. And it cannot judge whether a claim is true. Every post below makes one, a test result, a launch, a price, and those are the lines to read before you press approve.

Can you start an Instagram post from X with @bot?

Yes, if you are in the right country. Tag @bot in a post or reply on X and your main Bot takes the post as a task, so "@bot turn this thread into an Instagram carousel for Friday" would reach a Bot that has one of the plugins above. xAI's tagging page says it is not yet available for X accounts based in Australia, the United Kingdom, the European Union, Iceland, Liechtenstein or Norway, and that a VPN makes no difference because it goes by the country on your X account. If you are in Europe, @bot will simply not reply.

What the vendor guides get wrong

The vendors that get it most right are the ones that say the least: AdaptlyPost and Hermoso both state plainly that only Business and Creator accounts can be published to, and Hermoso that Meta's API has no scheduling and no drafts. Two of them, AdaptlyPost and Hermoso, also offer shared Bot templates on x.ai, which carry xAI's own warning that the Bot "was created by a third-party user" and "may act on your behalf". Read what a template does before you add it.