// Build a social media publishing calendar

Build a social media publishing calendar

Turn an approved content plan into a social media publishing calendar with safe, scheduled InvisibleAPI jobs.

Publishing calendar

Next week

Review
M14T15W16T17F18S19S20
09

Launch story

@acme.official

Review
12

Customer proof

@acme_hq

Ready
16

Weekly tip

Instagram + X

Draft
18 / 100 postsquota
01 / Build it in Claude

Start with the prompt, then make it yours.

Paste this into Claude, then give it your content plan and scheduling rules.

Claude / Build a social media publishing calendar
Build a social media publishing calendar for our content plan. Connect to the InvisibleAPI MCP server using our organization credentials. First, read our connected accounts and remaining publishing allowance. Ask for or ingest our approved content plan: captions, public media URLs, target accounts, allowed posting windows, minimum spacing, and account-rotation rules.

Draft a schedule for my approval before creating anything. After I approve a slot, create one scheduled publishing job per post using `requestedPublishAt` and a unique `clientRequestId`. Return the booked calendar with each job's status. Never publish or schedule a post without my explicit approval. If a planned slot exceeds an account's allowance or violates a platform rule, explain the problem and suggest the next valid slot.

This social media publishing calendar template is for teams that want Claude to do the calendar work without giving up control. It turns an approved content plan into scheduled InvisibleAPI publishing jobs, while you keep the final say on every slot.

What you build

You get a scheduler that can read a week of posts, respect time windows and spacing rules, rotate connected accounts, and show the finished calendar back to you. It drafts first. It only books jobs after you approve the slots.

Before you paste the prompt

  • Connect the InvisibleAPI MCP server with organization credentials that can read and publish.
  • Connect the Instagram or X accounts that belong in the schedule.
  • Prepare captions and publicly accessible media URLs. InvisibleAPI does not upload media for you.
  • Decide the rules Claude should follow: allowed posting windows, minimum spacing, rotation order, and who approves a draft schedule.

What happens after you approve the schedule

  1. Claude resolves the connected accounts and checks the remaining publishing allowance.
  2. It turns each approved post into one scheduled publishing job with requestedPublishAt.
  3. Each job receives a unique clientRequestId, so a retry cannot create a second post.
  4. It returns the booked calendar and the live status of every job.

Scheduling is job-based. Creating a job does not mean the post is already published. You can cancel a scheduled job before dispatch, and the platform reports any failed delivery with the detail needed to act on it.

Make the scheduler fit your team

  • Editorial teams: ask Claude to reserve a review step before every schedule is approved.
  • Agencies: group posts by client account, then require account-level approval before booking.
  • High-volume calendars: add a maximum number of posts per account and ask Claude to defer overflow to the next valid window.
  • Cross-platform campaigns: let the scheduler flag content that does not fit X before it creates a job. X text is limited to 280 characters, and image carousels allow up to four images.

FAQ

Does the calendar publish without a person approving it?

No. The prompt explicitly requires Claude to show the proposed schedule and wait for approval before it creates a scheduled job.

Can it schedule both Instagram and X posts?

Yes. Instagram and X are live today. The scheduler reads your connected accounts and applies the relevant platform rules before it books a job.

What happens when a post is retried?

Each scheduled job has a unique clientRequestId. Repeating the same request does not create a duplicate post.

// Related templates

Ship your first publish job today.

7-day free trial. Instagram and X, one API, MCP included.

Or talk to a human. support@invisibleapi.ai