You can schedule social media posts with Claude by connecting your accounts to Zernio, a single API that sits in front of 16 social platforms. Claude reads the video and the captions from your computer, uploads them through Zernio, and schedules every platform from one instruction. I schedule all of VPPA's shorts this way.
This post expands a 52-second video I published on September 20, 2026. It's embedded below.
Key takeaways
- One sentence replaces the scheduling tab. I tell Claude which video, which platforms and what time, and it schedules the post everywhere.
- Zernio is the piece that makes it possible. It's one API in front of 16 social platforms, so Claude talks to one service instead of YouTube's, LinkedIn's and X's APIs separately.
- Each platform still gets its own caption. Claude sends different text to Instagram, LinkedIn, YouTube and X inside the same request.
- The video below was scheduled this way. A 53 MB file went out to 4 platforms from one instruction, set for 8:15pm Eastern.
- It works from your phone. If your Claude or Codex session is reachable remotely, you can schedule reviewed content while you're out on a walk.
Watch it on YouTube · Instagram · LinkedIn · X
Have you ever fantasized about just telling Claude to schedule all your posts, and having it happen? I have. Scheduling was the boring last step after the content was done: open four tabs, upload the same file four times, paste four captions. Now it's a sentence, and I'm not going back.
How do you schedule social media posts with Claude?
You give Claude two things: access to the folder where your finished content lives, and an API key for a scheduling service that is connected to your social accounts. Then you tell it what to post and when.
Claude has no built-in connection to Instagram or LinkedIn. It needs something on the other end that is allowed to publish on your behalf. For us that's Zernio. The setup looks like this:
- Connect your accounts to Zernio. You click "connect" per platform and approve on a login screen that Zernio hosts. No developer apps to register.
- Create an API key and store it outside your project. Ours sits in a small file in my home folder that only my user can read. Claude loads it when it needs it and never prints it.
- Give Claude access to your content. I run Claude Code on my Mac, so the finished videos and caption files are just folders it can read. Content in the cloud works too, as long as Claude can reach it.
- Have Claude write the scheduling script once. Ours is a short Python script Claude wrote against Zernio's API docs. It uploads the video, builds one request with a caption per platform, and sets the time. Zernio also ships an MCP server if you'd rather skip the script.
- Ask for a dry run. Claude prints exactly what it's about to send, per platform, before anything leaves your computer.
- Say the sentence.
Here's the actual sentence I typed for the video on this page: "Let's schedule it to all my socials, using Zernio, at 8:15pm eastern, today, please." That was the whole job.
What is Zernio?
Zernio is a unified social media API: one service that connects to your social accounts and exposes a single, consistent way to post, schedule and pull analytics across all of them. Its own site describes it as a "developer-first REST API and hosted MCP server" covering 16 social platforms, including Instagram, YouTube, LinkedIn, X, TikTok, Facebook and Threads.
In the video I call it a central hub for all the social media APIs, and that's the right mental model. You connect once to Zernio. Zernio stays connected to everything else.
Pricing at the time of writing, from their homepage: the first 2 connected accounts are free, then $6 per account for the first 10. We run 4 accounts on it (Instagram, LinkedIn, YouTube and X).
Why not connect Claude to each platform's API yourself?
Because every platform's API is its own project, and some of them won't let a small team publish at all without an approval process.
YouTube is the clearest example. Google's documentation for the upload endpoint says that videos uploaded from unverified API projects "will be restricted to private viewing mode," and that lifting the restriction requires an audit of your API project. We ran into this when we looked at automating uploads for a client's highlights channel: the upload works, the video just can't go public. Then add LinkedIn's app review, Instagram's requirements for publishing Reels, and X's paid API tiers. Each one has different logins, different upload flows and different rules.
A unified API has already been through all of that. You inherit its approvals. For an agency our size, that's the difference between "scheduled tonight" and a separate integration project for every platform.
What does Claude actually send to each platform?
One request, with different content per platform. This matters, because a LinkedIn post and an X post are not the same piece of writing. Here's what went out for this video:
| Platform | What Claude sent |
|---|---|
| The video as a Reel, shared to the feed, with its own caption and 5 hashtags | |
| The video on my personal profile with a longer, 1,541-character post | |
| YouTube | A Short with its own title, description and tags, set to public, in the Education category |
| X | A 229-character post carrying the video, plus a reply underneath |
The captions themselves come from another step in the same system. Claude writes them from the transcript using our SEO captions skill, saves them to a file, and the scheduling script reads that file. I covered why those captions matter in this post on social media post descriptions and SEO.
So far we've scheduled 6 VPPA shorts this way, the first 4 as a single batch.
Can you schedule posts from your phone?
Yes, if the Claude or Codex session that has access to your content is one you can reach remotely.
This is the coolest part for me. You can be out on a walk and say to your phone: go to the content that's ready, the content that was just reviewed, and schedule it. The session on the other end has the files and the API key, so it does exactly what it would do if you were sitting at the desk.
The condition is where your files live. If finished videos sit on a laptop that's asleep, nothing remote can reach them. Keep approved content somewhere the session can always read, whether that's a machine that stays on or cloud storage.
Who this is for (and who it isn't for)
This is for people who already produce content in volume and already use an AI agent for other work: founders posting daily, small content teams, agencies like ours that schedule for several accounts. If you're writing captions with Claude anyway, having it also press "schedule" removes the last manual step.
It isn't for someone posting twice a month. A normal scheduling app with a calendar view is simpler, and you won't earn back the setup time. It also isn't for anyone who wants zero review. Claude schedules what a human approved. I would not let it decide on its own what gets published under my name.
Common mistakes when you let Claude schedule your posts
- Sending one caption to every platform. The API lets you set text per platform. Use it.
- Skipping the dry run. A scheduled post with the wrong caption is public the moment it fires. Make Claude show you the request first.
- Sending a time without a time zone. We always send the offset explicitly, like
2026-09-20T20:15:00-04:00. "8:15pm" alone means something different to a server in another country. - Trusting a tutorial over the API's own spec. The first field name we used for per-platform captions was silently ignored, and every platform got the same text. The spec had the right name. Point Claude at the spec.
- Hitting retry on a post that's already scheduled. If one platform fails, check the status per platform and re-run only what failed. Otherwise you risk a double post on the platforms that worked.
- Pasting the API key into the chat every time. Store it once, outside the project folder, readable only by you.
I'm super bullish on this kind of setup. Obviously the scheduling itself was never the hard part of content. But it was the step I kept putting off once a video was done, and that step is gone now.
Frequently asked questions
Can Claude post to Instagram or LinkedIn directly?
No. Claude has no built-in connection to your social accounts. It needs a service that is authorized to publish for you, reached through an API or an MCP server. We use Zernio for that.
Is Zernio free?
At the time of writing, Zernio's homepage lists the first 2 connected accounts as free, then $6 per account for the first 10 accounts, with lower per-account prices above that.
Do I need to know how to code to set this up?
No. Claude wrote our scheduling script from Zernio's API docs. You do need to describe clearly what you want: which platforms, which caption goes where, and what a dry run should show.
Does this work with Codex or other AI agents?
Yes. Zernio is a regular REST API with an MCP server on top, so any agent that can make web requests or use MCP tools can schedule through it. I mention both remote Claude and remote Codex in the video.