Creator OS
2026apiautomationinstagramn8n

n8n Instagram Posting Workflow: 2026 REST API Setup

Build an n8n Instagram posting workflow that actually publishes: the REST API node, the 25-post limit, and a working setup that scales to TikTok, LinkedIn and Facebo

Creator OS · November 5, 2026 · Updated November 13, 2026 · 9 min read

To do n8n Instagram posting in 2026, call a posting API from an HTTP Request node. Creator OS provides a REST API keyed with a cos_live_ token, so one workflow can create an Instagram Reel, a TikTok video and a LinkedIn post from the same run. No custom node and no per platform wiring.

n8n workflow
  [Schedule Trigger]
        |
  [Set: caption + media url]
        |
  [HTTP Request: POST /v1/posts]
        |  Authorization: Bearer cos_live_...
        |  content, platforms, media, schedule_at
        v
  Creator OS  -->  Instagram (Reels, images, carousels, Stories)
              -->  TikTok, LinkedIn, Facebook, YouTube, X, Threads
        |
  [Webhook: post.published / post.failed]
One HTTP Request node replaces a stack of platform specific nodes.

What does n8n Instagram posting require in 2026?

You need three things: a connected Instagram Business or Creator account, a credential n8n can send on every request, and an endpoint that creates the post.

Creator OS connects Instagram with a sign-in step in the web app. On the platform side, Instagram requires a Business or Creator account, and Creator OS handles each format’s rules for you: Reels, feed images, carousels and Stories. The caption, media and schedule all go in one request body.

The credential is a Creator OS API key from Settings > API keys. It is pinned to one workspace, which is one set of socials. An agent or workflow holding that key cannot post to another workspace. If you want a key that can only read, create a read-only key on the same screen.

Nothing about this requires a Facebook app or a review queue inside your n8n project. You store the key as an n8n credential and reuse it in every HTTP Request node.

Get started for $0

How to build an n8n Instagram posting workflow with the Creator OS REST API

Build it as four nodes: a trigger, a Set node for the caption, an HTTP Request node and an optional webhook for the result.

Start with an HTTP Request node and these settings:

Field Value
Method POST
URL base URL + /v1/posts (base URL is in the docs)
Authentication Header Auth, name Authorization, value Bearer cos_live_...
Body content type JSON

The simple form of the body is short:

{
  "content": "Three ways to cut a Reel hook. Full clip in bio.",
  "platforms": ["instagram"],
  "media": ["https://example.com/hook.mp4"],
  "schedule_at": "2026-03-02T14:00:00Z",
  "timezone": "America/Toronto",
  "post_type": "short_video"
}

media accepts a public URL or a med_ id returned by POST /v1/media. Upload once, reuse the id on every platform in the same run. That saves you from hosting the same file three times.

Drop schedule_at and the post goes out immediately. Keep it and Creator OS holds the post until that time, which means the n8n run can complete in seconds and you don’t need a wait node.

For a finished signal, create a webhook for post.published and post.failed and point it at an n8n Webhook trigger. Each event is signed with X-CreatorOS-Signature, so you can verify it before you branch. The webhooks docs show the payload shape.

Before you go live, check the caption against each platform’s limits with creatoros validate:post-length --text "your caption". It is faster than discovering the problem from a failed post.

Instagram posting API vs the Graph API: which node should n8n call?

Call whichever endpoint you can operate reliably. Creator OS wraps the platform rules so the request stays the same across networks.

Creator OS posting API Instagram Graph API directly
Auth One cos_live_ key per workspace Meta app, tokens, permissions
Formats Reels, images, carousels, Stories through one endpoint Separate calls per format and media type
Other networks Same request adds TikTok, LinkedIn, Facebook, YouTube, X, Threads, Reddit, Discord, Slack Instagram only
Errors One shape: { error: { code, message, status } } Meta specific error objects
Scope Key pinned to one workspace; read-only keys are refused on writes Per app and per account

The Graph API is the direct route and gives you every raw field. The Creator OS route gives you one credential and one body shape, and it tells you which platforms were skipped. Networks named in a post that aren’t connected come back in missing_platforms, and the rest still go out. That single field is why a mixed-network workflow rarely dies halfway through.

For the trade-off between API styles, see MCP server vs REST API posting.

How to keep an n8n Instagram posting run inside the daily limit

Treat your daily publishing cap as a ceiling the workflow checks before it posts, not an error you discover afterwards.

A daily content run that touches 30 items at once is a fragile design. Two habits prevent trouble. First, keep a small data store in n8n (or a Google Sheet) with a counter per account per day. Before the HTTP Request node, an IF node stops the run when the counter reaches your limit. Second, prefer the API’s own scheduling. Send ten posts with different schedule_at values in one run rather than firing ten separate triggers across the day. You get the same spread with one execution and one place to watch.

When Creator OS rejects a post, it returns an error object rather than a silent drop. Add an IF node on error.code and route the overflow to tomorrow’s slot. If your item is a Reel for non-followers, you could also consider Trial Reels, which are set with trial_reel in the same endpoint. Instagram only allows them on accounts with 1,000 or more followers, and Creator OS refuses the post below that with trial_reel_needs_followers, suggesting a regular Reel instead. Read how scheduled Instagram posts behave before you batch too many.

Can one n8n workflow post to Instagram, TikTok, LinkedIn and Facebook at the same time?

Yes. The platforms array is the only thing that changes.

{
  "content": "New episode is live. Link in the first comment.",
  "platforms": ["instagram", "tiktok", "linkedin", "facebook"],
  "media": ["med_8f2k1"],
  "schedule_at": "2026-03-02T14:00:00Z",
  "timezone": "America/Toronto"
}

Creator OS applies each platform’s rules inside that one call. TikTok needs privacy and consent flags, and the simple form fills them. YouTube turns a vertical short video into a Short automatically. LinkedIn takes a first comment, and Instagram has no clickable links in captions, so the same link often belongs in firstComment on several networks.

When a platform needs its own settings, switch to the advanced form: platforms becomes an array of objects with platform, account_id, options and content. TikTok settings sit in a top-level tiktok object. Use account_ids to narrow a post to specific accounts when one network has several.

That pattern is the whole reason to keep the multi-network request in one node. Splitting it into four branches means four retries, four error shapes and four captions to keep in sync. If you would rather an AI agent own the loop, this walkthrough on posting to Instagram and TikTok at once covers the MCP route, and the KevBuildsApps YouTube channel has working builds.

Instagram posting API errors n8n builders hit and how to fix them

Almost every failure is one of four things: a missing connection, a caption that breaks a platform limit, a missing media id, or a schedule in the past.

  • Platform missing. The response lists missing_platforms. Connect that account in Creator OS and rerun. The rest of the post already went out, so don’t resend it.
  • Read-only key. A key created as read only is refused on writes. Create a read and write key in Settings > API keys and update the n8n credential.
  • Caption rejected. Run creatoros validate:post-length --text "..." against the draft. Threads caps a post at 500 characters, and the check tells you before the API does.
  • Media not found. A med_ id belongs to one workspace. If you copied an id from another environment, upload the file again with POST /v1/media.
  • Wrong error parse. Every error uses { error: { code, message, status } }. Read error.code in your IF node, not the top-level message.

One more habit: store the post id Creator OS returns in your data store before you continue. If n8n retries a failed execution, check the store first so you don’t post twice. The posts API reference lists every field and response code. If you’d rather not hand-build the request, creatoros posts:create --text "..." --platforms instagram,tiktok --media med_8f2k1 --scheduledAt 2026-03-02T14:00:00Z --timezone America/Toronto does the same thing from a terminal, and you can paste the working command into an Execute Command node while you debug.

FAQ: n8n Instagram posting questions

Is there an official n8n Instagram posting node?

Most n8n Instagram workflows use the HTTP Request node or a community node, because posting to Instagram is a series of API calls rather than one action. Creator OS gives you one endpoint and one credential, so a stock HTTP Request node is enough and you don’t depend on a community node keeping up with the platform. The request body is documented at the posts API docs.

How do I post to Instagram from n8n without building my own Meta app?

Connect your Instagram account inside Creator OS once, then send a Creator OS API key from n8n. The key is scoped to one workspace and one set of socials, so a leak in one workflow cannot touch another client’s accounts. Your workflow then calls POST /v1/posts with platforms: ["instagram"] and the media URL.

What limits should an n8n workflow check before posting to Instagram?

Check your own per account daily cap before the HTTP Request node and branch on error.code when Creator OS rejects a post. Instagram accounts also have rules Creator OS applies for you, including the 1,000 follower minimum for Trial Reels, which returns trial_reel_needs_followers below that line. A counter in a data store plus the API’s scheduling keeps a batch run from failing partway.

Is there a social media posting API that works for Instagram, TikTok, LinkedIn and Facebook at the same time?

Yes. Creator OS takes a platforms array in one request and applies each network’s rules, so a single node publishes to all four. Platforms you haven’t connected come back in missing_platforms while the connected ones still publish. Creator OS covers 11 platforms plus Skool from the same workspace.

How do I schedule Instagram posts from n8n at a fixed time each day?

Use a Schedule Trigger for the run, then set schedule_at and timezone in the post body and let Creator OS hold the post. The n8n execution finishes immediately, so you don’t need a Wait node or a long-running workflow. Listen for post.published on a webhook to confirm it went out.

Get started: connect the Creator OS API to n8n in under 10 minutes

Create an account, connect Instagram, TikTok, LinkedIn and Facebook in the web app, then copy a cos_live_ key from Settings > API keys. Paste it into an n8n Header Auth credential, point an HTTP Request node at /v1/posts, and send one test post to a single platform before you widen the platforms array. The base URL and every field are at https://www.creatoros.ca/docs.

Sign up at https://www.creatoros.ca/sign-up. Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. Watch the builds on KevBuildsApps and the launch video if you want to see the workflow before you build it.

Get started for $0
Free trial for new subscribers. Cancel anytime.

Keep reading