How-To Guide

How do you automate social posting with Zapier or n8n, and where does it break?

Build a status-table posting workflow in Zapier or n8n, then see where it breaks: no X app in Zapier, Meta and X limits, per-post fees and double posts.

11 min read

By the Superdirector editorial team. Zapier, n8n, X and Meta documentation read November 7, 2026; Meta's container-status section rechecked November 11, 2026; the Zapier AI and MCP pages and n8n's AI Agent node page read November 14, 2026; revised November 14, 2026.

At a glance

How do you automate social posting with Zapier or n8n, and where does it break?

Keep your posts in one table with a status column, start the workflow when a row is marked approved, check the caption and media, publish with the platform's own action, and write the post ID back. Zapier has ready Instagram actions but no X app since August 31, 2023; n8n has an X node and reaches Instagram through Meta's publishing calls. The workflow breaks on account rules, Meta and X limits, X's per-post fees, and replays that publish twice.

  • Zapier: Instagram photos, carousels and Reels yes; X no native app since August 31, 2023.
  • n8n: an X node yes; Instagram through Meta's publishing calls with the Facebook Graph API or HTTP Request node.
  • X charges $0.015 per create-post request and $0.200 with a URL; Meta's own pages give 50 and 100 as the Instagram cap, so plan around 50.
  • Store the post ID and check it before any publish, replay or retry.
  • An AI step can draft the caption into the table; the approval status and the publish steps stay as they are.
Five numbered steps left to right, queue, trigger, check, publish and write back, each with a short cue for the row, the approval, the media check, the limits and the post ID.

The five-step posting pipeline this guide builds, one row per post. Original diagram from the guide's own Zapier and n8n build sections.

Posting queue template (CSV)

Superdirector

Make it work for your brand

Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.

The short answer: a status table, a trigger, a check, a publish step and a write-back

Keep your posts in one table with a status column, start the workflow when a row is marked approved, check the caption and media, publish with the platform's own action, and write the platform's post ID back to the row. Zapier has ready Instagram actions for photos, carousels and Reels, but no X app since August 31, 2023. n8n has an X node, and it reaches Instagram through Meta's publishing calls: its Facebook Graph API node fits Meta's Facebook Login route, and its HTTP Request node fits either route. The workflow breaks on account rules, Meta and X limits, X's per-post fees, and replays that publish twice.

This table shows what each tool offers for each destination, as read on each vendor's own pages on November 7, 2026. The last column is the catch the platform sets, which no tool removes.

DestinationZapiern8nCatch the platform sets
Instagram photos and carouselsInstagram for Business app, Publish Photo(s): one photo or a carouselNo Instagram node in the built-in app list; call Meta's publishing endpoints with the Facebook Graph API node (Facebook Login route) or the HTTP Request node (either route)Business or Creator account; Page Publishing Authorization if the linked Page needs it
Instagram ReelsPublish Video action posts a ReelSame route as photosVideo containers have a status to check before publishing
X postsNo native app since August 31, 2023; Zapier points to Buffer or HootsuiteX node: create or reply to a postX developer account; $0.015 a post, $0.200 with a URL; 100 per 15 minutes per user
LinkedInLinkedIn app; its templates create company updatesLinkedIn node: create a post as a person or organisationNot covered here: LinkedIn's own API rules were not read
YouTube videoYouTube app with an Upload Video actionYouTube node: upload a videoNot covered here: YouTube's own quota and review rules were not read

TikTok, Facebook Pages and Threads are not in this guide. We did not read their publishing rules, so we make no claim about them; read each platform's developer pages before you build a workflow for it. The pattern below, a status table, a trigger, a check, a publish step and a write-back, carries over to any destination your tool can reach.

Keep every post in one table with a status column

Both tools need something to read from, and a table is the least fragile choice. Use a Google Sheet, an Airtable base or Zapier Tables. One row is one post for one platform: caption, media link, publish time, status, the platform's post ID, a count of attempts and the last error. Posting the same idea to Instagram and X takes two rows, because the formats differ (see crossposting).

The status column is the whole control system. It moves from draft to approved to publishing to published, or to failed. A person changes draft to approved; the workflow changes the rest. If you do not yet have a calendar to fill it from, our content calendar guide shows how to build one.

Download the queue template for the columns and a rule we recommend: set the status to publishing before the publish step, store the platform's post ID when it returns, and never run the publish step for a row that already has one. That rule is ours, and it is the cheapest defence against double posts.

Here is how we would build it. In Zapier, the trigger fires when a row changes. A Filter step lets the run continue only when two things are true: the status is approved, and the platform_post_id column is empty. The first action then updates the row's status to publishing, the next action publishes, and the last action writes the post ID and sets the status to published. Because the first action moves the status away from approved, a second trigger on the same row stops at the Filter.

In n8n, an IF node does the same job with two conditions: {{ $json.status }} is equal to approved, and {{ $json.platform_post_id }} is empty. Only the true branch continues, to a sheet node that sets the status to publishing, then the publish call, then a sheet node that writes the post ID. Leave Retry On Fail off on the publish node, for the reason in step 5.

This is a guard, not a true lock. A sheet cannot stop two runs that start in the same second from both passing the check, so point one workflow at one table. And if a row sits at publishing with no post ID, the publish call may have worked without telling you: look at the profile before you set it back to approved.

Start from a Google Drive folder instead of a table

The steps above start from a row in your table. They can start from a Drive folder instead. Zapier's Google Drive app has a "New File in Folder (Realtime)" trigger that fires "when a file is added to a chosen folder or shared drive", so the folder becomes the queue. n8n's Google Drive node offers File/Folder "Search files and folders" plus a "Download a file" operation, so the same folder can feed the run in place of a sheet row. Either way, treat the folder as the trigger, not as the media host: the caption check and the approval step still decide whether a post may go out.

A Drive share link will not work as the media URL. Blotato's guide to Google Drive to Instagram automation, read November 14, 2026, states the rule the check in step 3 applies: Instagram "will not accept a Google Drive share link as media" and "wants a real hosted URL". Its builds download the file, then upload it to a separate image host that returns a public URL, because Meta fetches the media from a publicly accessible server at publish time. The upload step is the one most DIY builds leave out.

Two settings from that guide carry over. Cap what one run picks up: its n8n build turns the search node default down, because "the search node defaults to 50, not 2", and its Make build sets the Limit field, "which is the maximum number of files pulled per run". And expect a delay: "Drop a file and it goes out on the next run, not the moment you release the mouse", so a Drive-triggered pipeline still runs on its schedule. That guide's publish step is a vendor service of its own, so what carries over to this guide is the folder wiring and the hosting step, not its vendor choice.

Keep the table and the post-ID rule either way. A Drive trigger decides when a post enters the pipeline, not whether it may publish: the caption and media check still runs, the status still moves to publishing before the call, and the post ID is still what marks the row done. If the file name carries the caption or the destination, read it in a step before the check, so the publish step receives a hosted URL and a checked caption, not a Drive link.

Trigger on approval, not on creation

Trigger on the status change, not on a new row. In Zapier, use an update-row trigger and add a Filter step so the Zap continues only when the status is approved. Zapier says its Instagram triggers are polling triggers, so "there may be a delay" between an event and the run, and its YouTube app page shows polling triggers checking every 15 minutes on the Free plan. Leave a margin on any scheduled time.

In n8n, use a Schedule Trigger that reads approved rows whose publish time has passed, or a webhook that your sheet calls. Both work. A schedule is simpler and survives a missed call, and a webhook is quicker. Either way, publish times are yours to enforce, not the tool's: neither platform's page we read gives you a guarantee that a run starts at the minute you set.

Two lanes: a person makes the one move from draft to approved, and the workflow moves publishing to published with the post ID saved.

Only draft to approved is a person's move; the workflow does the rest. Original diagram from the queue template this guide recommends.

Check the caption and media before publishing

Check the media first. Meta fetches your file by URL, and its content publishing guide says "the media must be hosted on a publicly accessible server at the time of the attempt." A link that needs a sign-in will not work. The same guide says JPEG is the only image format supported, and a carousel can hold up to 20 items. A PNG export from a design tool needs converting before it reaches the publish step.

Add a gate that stops the run, marks the row failed and writes the reason to the last-error column when any of these is true: the media link does not open without signing in, the file is not a JPEG for an image post, the carousel has more than 20 items, or the caption is empty. In Zapier that is a Filter plus a Paths branch. In n8n it is an IF node. Both leave the post unpublished and tell you why.

Meta's media_publish reference also lists a rule no tool can fix. If the Page connected to the Instagram account requires Page Publishing Authorization, "PPA must be completed or the request will fail." Complete it once, before you build anything.

Publish with the platform's own action

For Instagram, Zapier's Instagram for Business app is the quicker route. It needs a Business or Creator account linked to a Facebook Page, and a Facebook user with permission to create content on that Page. Its Publish Photo(s) action posts a single photo or a carousel, and Publish Video posts a Reel. Personal accounts cannot connect.

In n8n the same result takes more work, and the node you use depends on how you sign in to Meta. Meta's content publishing guide lists separate routes. The Instagram Login route uses Business Login for Instagram and an Instagram User access token on graph.instagram.com; InvisibleAPI's guide adds that this route needs no Facebook Page. The Facebook Login route uses a Facebook Page access token on graph.facebook.com. n8n's Facebook Graph API node sends its requests to graph.facebook.com, or to graph-video.facebook.com for video uploads, so it suits the Facebook Login route: you set its Node to your Instagram account ID and its Edge to media, then to media_publish. For the Instagram Login route, use the HTTP Request node. Either way you follow Meta's steps: create a container, upload the file first if it is a resumable video upload, then publish the container. This is our reading of the n8n and Meta pages; we have not run either route end to end.

For X, the two tools differ most. Zapier removed its Twitter integration on August 31, 2023, "due to Twitter's decision to change its API policy and pricing," and its own Twitter app page still says the integration has stopped working. Zapier suggests Buffer or Hootsuite for posting to Twitter. On Professional, Zapier's pricing page lists Webhooks, which could call X's API directly; we did not test that route. n8n has an X node whose operations include creating or replying to a post. It needs an X developer account and an OAuth 2.0 credential, and n8n's credential page warns that the credential is "subject to app rate limits."

X's cost model is what usually surprises people. The X API is pay-per-use: its pricing page lists $0.015 for a create-post request and $0.200 for a create-post request that includes a URL, and adds that prices are subject to change. By our arithmetic, five text posts a week cost $0.075 a week, or about 32 cents a month, but a post that includes a link costs more than thirteen times as much. The page does not say whether a link added in a reply is billed the same way, so test that before you rely on it. For Instagram, none of the Meta pages we read lists a fee for publishing calls, and InvisibleAPI's guide also says Meta publishes no usage fee. That is an absence on the pages we read, not a promise from Meta, so check Meta's terms before you budget.

For LinkedIn, both tools can create posts. For comparing wider options, our guide to the best AI tools for social media marketing puts these tools next to dedicated schedulers.

Write the result back and alert on failure

The last step writes the platform's post ID to the row and sets the status to published. The ID is your proof the post exists, and your protection when something retries.

Add an alert path to every run. In n8n you can set an error workflow in Workflow Settings that "runs if an execution fails," and it must start with the Error Trigger node. In Zapier, add an error handler path; its task usage page notes that successful steps in an error handler path count as tasks. Use either to send yourself a message with the row and the error.

A success reply is not always the end of the story, so confirm the post before you mark it published. Meta's content publishing guide covers the case where a video container was created but the publish call "does not return the published media ID": you can then read the container's status_code field to see what happened. One of the values it lists is PUBLISHED, meaning the media has gone out. For a video container, such as a Reel, Meta recommends checking "once per minute, for no more than 5 minutes." Meta gives this check for video containers only; for a photo or carousel with no ID returned, look at the profile before you retry. In Zapier that is a Delay step and a Webhooks request on a multi-step plan; in n8n it is a Wait node and an HTTP Request node. If the status says PUBLISHED, write it to the row and stop. Do not publish again.

Run that check on Meta's own bound and stop there, because the guide's rule already sets the limit: one status read per minute, for no more than five minutes. Our rule narrows it: wait, read the container status once, and if it is not PUBLISHED, send yourself an alert with the row and stop, and let the weekly check close it out. A run that checks once and alerts is short and cheap to reason about, and a run that keeps asking inside itself is the kind that surprises. The five-minute window, the status field and the PUBLISHED value are Meta's; the single-read-and-alert bound is ours.

Keep scheduled separate from published as well. A run that starts at its scheduled time confirms that the workflow fired, not that a post went out, and neither vendor page we read promises a run starts on the minute you set, so the trigger section's margin advice still applies. Give rows waiting on their time the status scheduled, and count scheduled rows in the weekly check the same way you count everything else: a row is settled only when it holds a post ID, or, for a video container, when the status read says PUBLISHED. Until then, scheduled is a promise to post, not a post.

Then think about repeats. Zapier's task page counts "previously successful steps that run again when you replay an entire Zap run." If the publish step succeeded and a later step failed, replaying the whole run runs the publish step again. n8n's Retry On Fail setting "automatically tries the request again if it fails the first time." If the platform posted and the response never reached n8n, a retry can post a second copy, which is why we leave it off on the publish node. Neither vendor page says it will duplicate a post, and both are consistent with it. The status and post-ID rule above is what stops it: before you replay a run by hand, open the row, and if it already has a post ID, do not replay the publish step.

Keep a short weekly check as well. Once a week, open the tool's run history, read every failed run, and compare the rows marked published with what is actually on the profile. A row that says published with no post on the profile, or a post on the profile with no row, means the write-back or the trigger has drifted. This routine is ours; neither vendor page we read sets one.

Three confirm paths after the publish step: an ID returned means save and stop; a video with no ID means read the container status once, where PUBLISHED ends it; any other post with no ID means check the profile before retrying.

What to do when the publish step ends, by outcome. Original decision diagram based on Meta's content publishing guide, read November 11, 2026.

One pipeline per platform

The five steps above build one loop for one post, and the table rule at the start of this guide already sets its shape: one row is one post for one platform. Posting the same idea to Instagram and X is two rows and two publish steps. In Zapier you build that as branches inside one Zap or as two small Zaps over one table; in n8n, as branches in one workflow. Each branch carries one destination's publish call, its confirmation and its write-back, and each publish step is one more action counted the way the cost section counts. One run publishes one destination per branch, so a second destination doubles the publish and confirm work rather than the tool.

The route table near the top of this guide shows which tool can reach which destination. This map adds the two columns that route table leaves out: how each destination confirms a post, and what to write back. Read the confirm column together with Meta's five-minute rule from the previous section.

DestinationPublish callHow it confirmsWhat you write back
Instagram photo or carouselZapier's Publish Photo(s) action; n8n's container then media_publish, per the routes aboveA publish reply usually carries the media ID. Meta's container-status read is written for video containers, so a photo with no ID returned is confirmed on the profileThe media ID, then the status published
Instagram ReelZapier's Publish Video action; n8n's video container then media_publishOn our bounded rule: one status read inside Meta's five-minute window. PUBLISHED settles the row; anything else goes to the alert pathThe container status first, the media ID once it reads PUBLISHED
X postn8n's X node; Zapier has no native app, so a scheduler Zapier lists or a Webhooks call you maintainOne exchange: the call succeeds or returns an error, and a 429 means a rate limit or a usage cap on X's error pageThe platform's post ID, or the row's last-error column
LinkedIn postZapier's LinkedIn app; n8n's LinkedIn nodeNot covered here: LinkedIn's own API rules were not read for this guideThe row rule holds: an ID in the row before you call it published
YouTube videoZapier's YouTube app with an Upload Video action; n8n's YouTube nodeNot covered here: YouTube's own quota and review rules were not readThe row rule holds: an ID in the row before you call it published

One publish call reaches one account. A second account on the same platform is a second row and a second branch, so the map repeats per account rather than per platform. Each destination's account setup sits in the publish section above: the professional-account rule and the Facebook Page link for Meta, the developer account and per-post pricing for X. TikTok, Facebook Pages and Threads are not on the map: this guide did not read their publish rules, so it makes no claim about them, and the loop above carries over to them only once you have a publish call you can reach.

Add AI steps for drafting, never for the publish decision

The six steps above build a complete pipeline, and one kind of step can slot into it: an AI drafting step between the trigger and the caption check. Zapier draws the line itself: "AI handles a single task in a workflow, like writing or summarizing. Deterministic steps handle the rest." zapier.com/ai, its own AI page. In this workflow the AI step reads the row's brief and writes a caption draft into the caption column. It does not publish. A person still moves the row from draft to approved, and the run still starts on that status change.

Placed there, the AI step leaves the caption check in charge. A model-written caption is just text in the row, so it passes the same Filter and media rules as a typed one. Zapier's page lists the guards: "Run PII, prompt injection, and toxicity checks on AI steps." What a model cannot do is read Meta's limits for you; the check in step 3 is what decides whether the post may run.

In n8n the drafting step is the AI Agent node: "The AI Agent node lets you build an AI agent in n8n. Connect a chat model and one or more tools, and the agent decides which tools to call to complete a task." n8n's agent node page. The node must keep at least one tool sub-node connected, per the same page. Keep the agent's job bounded so its tools serve the caption draft in the row, and everything downstream stays in the workflow you control.

Zapier's MCP page describes the agent route as well: MCP "is a secure way to connect AI clients such as Claude, ChatGPT, and Cursor to the apps you use through Zapier," with Zapier managing the connections and access controls MCP page. When such a routine should keep running, Zapier says "you turn it into a Zap with a trigger, an owner, and a record of every run." Counting changes with it: each tool call "uses two tasks from your existing task quota," so an agent session spends the same task budget as the workflow it feeds.

Where AI does not go: the publish step, the container-status read, the post-ID guard and the write-back stay deterministic steps. Those are the moves the failure table and the cost example count, and they are what make the pipeline dependable. The weekly check in step 5 is where a drafting step earns trust: read what it wrote into the table the same way you read every failed run.

Where it breaks: nine documented failure points

These are the points where the pipeline stops or misbehaves, with the vendor page that states each. Limits that belong to the platform apply to either tool.

FailureWho sets itWhat the page saysWhat to do
X is not in ZapierZapierIntegration stopped August 31, 2023 and still shows as stoppedUse n8n, a scheduler Zapier lists, or an API route you maintain
A platform ends an API your tool usedMeta and ZapierMeta's Basic Display API ended on December 4, 2024, and Zaps built on Zapier's original Instagram app stopped that day (Zapier notice)Expect to rebuild when a platform changes; keep the table and move only the publish step
Account typeMeta, ZapierMeta publishes only to Instagram professional (Business or Creator) accounts. Zapier, and Meta's Facebook Login route (which uses a Facebook Page access token), also need the account linked to a Facebook PageConvert the account first; link a Page if you use Zapier or the Facebook Login route
Media rulesMetaPublic server at publish time; JPEG only; carousels up to 20 items; containers expire after 24 hours; 400 containers per account per rolling 24 hours (media reference)Check files in step 3 and publish within a day of creating a container
Instagram publishing capMeta50 posts in 24 hours on the media_publish reference and the guide's carousel section, 100 on the guide's rate-limit sectionPlan around 50, the lower figure, and read your live usage from the content_publishing_limit endpoint; at a few posts a day neither figure binds
X rate limitXCreate post: 100 per 15 minutes per user, 10,000 per 24 hours per app (X rate limits); a 429 means a rate limit or a usage cap (X error codes)Pace posts; read the error type to tell the two apart
X costX$0.015 per create-post request, $0.200 with a URL, prices subject to changeLeave links out of the post or budget for them
Task and execution allowancesZapier, n8nZapier counts successful action steps; n8n counts completed workflow executionsEstimate runs before choosing a plan (next section)
A repeat after a failureYour workflowZapier counts steps that run again on a full replay; n8n retries a failed nodeCheck for a post ID before every publish or retry

Third-party guides do not always match Meta's pages. InvisibleAPI's Instagram guide gives a carousel limit of 10 items where Meta's guide says 20, and states the 100-post cap without the 50 on Meta's reference page. bundle.social notes that X's 429 can come from three different counters, and X's own error page lists separate rate-limit and usage-capped types. When a number matters, read it on the platform's page the day you build.

What it costs to run: a worked example

The tools bill differently, so count before you pick a plan. This is our arithmetic for a founder who posts 5 Instagram carousels and 3 X posts a week, about 35 posts a month (8 posts times 4.33 weeks). Each post is one run: a trigger, a check, a status update to publishing, a publish step and a write-back.

Zapiern8n
What countsA task for each successful action step; triggers, Filter and Paths steps and errored steps do not countOne workflow execution for each run, however many steps it has
Our count for 35 posts a monthThree actions a run (set publishing, publish, write back) is 3 tasks: about 105 tasks. A failed row adds one task to record the reasonOne run per post: 35 executions
Plan allowanceZapier pricing: Free has 100 tasks a month and two-step Zaps only. Professional is listed from $19.99 a month (the page offers monthly and yearly billing), with multi-step Zaps; its task selector lists 100, 750, 1.5K and 2K tasks a month and upn8n pricing: Starter has 2.5K executions for 20 EUR a month billed annually. Pro: 10K for 50 EUR a month billed annually. The page we read lists prices in euros only. A self-hosted Community Edition is also available
What this meansFree does not fit: 105 tasks is over its 100, and a trigger plus three actions needs multi-step Zaps. Choose Professional at the 750-task tier and check the price the page shows for that tier35 executions is far below Starter's 2.5K; the cost is your time to build and keep up the workflow, plus the euro price at your bank's rate

These task rules are Zapier's for Classic Zaps. Its task page says that from December 1, 2026, Next Gen Zaps also use tasks, and each completed Next Gen run uses at least 1 task, so recount if you build in Next Gen.

Replays add tasks. Zapier says a full replay counts the steps that run again, so a post that fails at the write-back and is replayed uses its tasks twice. The numbers on both vendors' pricing pages are theirs and can change; the sources are in the limits sheet.

Worked example for 35 posts a month: Zapier at three tasks a run is 105 tasks, over Free's 100 so Professional at 750; n8n at one execution a run is 35 against Starter's 2,500; X adds $0.015 a post or $0.200 with a link.

Our arithmetic for a founder posting five carousels and three X posts a week. Original diagram with plan figures as each vendor listed them on November 7, 2026.

Zapier or n8n: which one to pick

If youPickBecause
Post mainly to Instagram and want it live todayZapierIts Instagram for Business app has photo, carousel and Reel actions ready
Post to X and do not want to run codeNeither alone, or a schedulerZapier has no X app; n8n's X node needs an X developer account and per-post credits
Want the workflow to call any API and keep error handling in your handsn8nIts HTTP Request node covers what a built-in node lacks, and an error workflow runs when an execution fails
Are not willing to maintain a workflow when a platform changes an APIA product that owns the whole loopBoth options ask you to rebuild when Meta or X changes something, as Zapier's 2023 and 2024 notices show
Already run other business workflows in Zapier or n8nStay in the tool you knowPosting becomes one more workflow you already watch, and its run history sits next to the rest
Need to decide what to post as well as how to post itNeitherBoth publish what you give them; finding formats that work is a separate job

Treat any automation as the end of a pipeline, not the start. Deciding what goes in the table is the hard part. Our 30-day batching guide shows one way to fill it, and content calendar automation covers the planning side.

When a managed account fits better than a pipeline

If your posts already flow through a bigger system you run, keep your own pipeline: the status table and post-ID rule above are what make it dependable. If what you actually want is for one brand account to keep posting while you do other work, building and maintaining the workflow may not be the best use of your week.

Superdirector, which publishes this guide, is built for that second case. Its headline is "Autonomous social media growth." That names what it is built for; it is not a promise of results. The $199-a-month plan is meant to run one brand's social account for you: it finds posts and formats taking off in your niche on Instagram, TikTok, YouTube and X, remakes them in your brand as carousels and X posts, fills the month's calendar, and posts Instagram carousels and X text posts on a schedule. You set the brand and creative direction, so you do not build the queue, trigger or write-back yourself. The $29-a-month plan is the hands-on entry: you work from Claude or ChatGPT and make assets yourself, without scheduled posting. Check the pricing page for the accounts and credits each plan includes before you choose.

Superdirector posts only those two kinds of post today; AI video and full autopilot are coming soon. You remain the publisher, and you label AI content where a platform requires it. See how it works.

Frequently asked questions

How do you automate social posting with Zapier or n8n, and where does it break?

Keep posts in a table with a status column, trigger on approval, check caption and media, publish with the platform's action, and write the post ID back. Zapier has Instagram actions but no X app since August 31, 2023; n8n has an X node and reaches Instagram through Meta's publishing calls. It breaks on account rules, Meta and X limits, X's per-post fees and replays that post twice.

Can Zapier post to X?

Not with a native app. Zapier's Twitter integration stopped on August 31, 2023 after Twitter changed its API policy and pricing, and Zapier's own page still says so. It points to Buffer and Hootsuite for posting to Twitter. A custom call to X's API is another route, which you would pay for per post.

Can n8n post to Instagram?

Not through an Instagram node: n8n's built-in app list has none. You call Meta's publishing endpoints instead. The Facebook Graph API node sends requests to graph.facebook.com, which suits Meta's Facebook Login route and needs a linked Facebook Page. For Meta's Instagram Login route on graph.instagram.com, which uses an Instagram User token, use the HTTP Request node. The account must be a Business or Creator account.

How much does it cost to post to X through the API?

X's pay-per-use pricing page lists $0.015 for a create-post request and $0.200 for one that includes a URL, and says prices are subject to change. The limits are 100 posts per 15 minutes per user and 10,000 per 24 hours per app.

Why did my automation post twice?

Most likely a replay or a retry ran the publish step after it had already succeeded. Zapier counts steps that run again on a full replay, and n8n's Retry On Fail repeats a failed node. Store the platform's post ID, let the run continue only when the status is approved and the post ID is empty, and leave Retry On Fail off on the publish node.

How do you confirm a scheduled post went out?

Treat the schedule and the publication as two confirmations. A run starting at its scheduled time proves only that the workflow fired, not that the platform received anything. Keep the row at scheduled until it holds the platform's post ID, or, for an Instagram Reel, until the container status read says PUBLISHED within Meta's five-minute window, and let the weekly check sweep scheduled rows that reached neither.

Where does an AI step fit in this workflow?

Between the trigger and the caption check, as a drafting step. Zapier describes AI steps as handling a single task such as writing while deterministic steps handle the rest; n8n's AI Agent node connects a chat model and one or more tools, and the agent decides which tools to call. Zapier's MCP connects Claude, ChatGPT or Cursor to app actions too, and every one of those tool calls uses two tasks from the same quota the Zaps use. The person still moves the row to approved, the publish step still runs on that trigger, and an AI-written caption passes the same media and length checks as any other. The publish step, the post-ID guard and the write-back stay deterministic.

Can you post to Instagram straight from a Google Drive link?

No. Instagram "will not accept a Google Drive share link as media", so the workflow downloads the file, uploads it to a host that returns a public URL and publishes from there, the same rule Meta's publishing page sets for any media. A watched Drive folder can still be the trigger: Zapier starts a Zap from a new file in a chosen folder, and n8n's Google Drive node searches and downloads from the folder. The publish decision stays with the approved row.

Related practical guides

Build the table first

Download the queue template, fill ten rows, and run one Instagram row through the pipeline before you add X or a second account.