Upload-Post and Flaghand both let an n8n workflow, a Make scenario or an AI agent send social posts through an API or an MCP server. They answer one question differently: can the automation publish by itself? With Upload-Post, a request made with your API key publishes now, at a set time or in the next queue slot. With Flaghand, the automation drafts and asks, and the post goes out only after the workspace owner approves that exact post with a passkey.
Every Upload-Post fact here was checked on October 26, 2026 on its own pricing section, full LLM guide, authentication, MCP server, text posts, webhooks, OpenAI Agents SDK and Vercel AI SDK docs, and its n8n and Make guides. Prices and features change; check those pages before you choose.
The short answer
- Choose Upload-Post if you post to Instagram, TikTok, YouTube or any of its other networks, want a free plan to start, are building posting into your own product, or want a workflow to publish without anyone approving each post.
- Choose Flaghand if your workflow or agent writes for a person who must approve exactly what goes out, and you want the server, not the agent's instructions, to enforce that.
Where Upload-Post is better
- Twenty-two platforms. It posts to TikTok, Instagram, YouTube, Facebook, LinkedIn, X, Threads, Pinterest, Reddit, Bluesky, Google Business Profile, Discord, Telegram, Slack, Mastodon, Nostr, Lemmy, Dev.to, Hashnode, WordPress, Whop and Listmonk, and its LinkedIn posting covers personal profiles and company pages. Flaghand posts to X and LinkedIn personal profiles; its TikTok posting is subject to TikTok's review.
- A free plan. Ten uploads a month on two profiles, with no credit card, though without TikTok. Paid plans have unlimited uploads.
- Ready-made integrations. Its own node ships with current versions of n8n, and it has Make, Zapier and Airtable guides, Python and JavaScript SDKs and a command line tool. Flaghand has no node or module of its own: you use n8n's HTTP Request, Make's HTTP module or Zapier's Webhooks, with the exact requests in Flaghand from n8n, Make, Zapier and GitHub Actions.
- Built for other people's accounts. Profiles group one client's accounts, a hosted connect page lets your users link their own, and white-label is included from the Professional plan.
- More than posting. Analytics, comments and DMs through the API and MCP, a video-processing API that adapts files to each network, and an AI tool that writes titles and hashtags for short videos. Flaghand's X read-back check isn't an analytics or inbox product.
Where Flaghand is better
- The approval is the server's rule. No API token can approve, schedule or post, so a leaked token, a looping workflow or a confused agent can't publish on its own.
- You approve what will actually post. The desk draws each post as X and LinkedIn show it, the check flags anything that wouldn't post as previewed, and the approval covers that exact snapshot.
- Links stay in X posts. Upload-Post removes every URL from X posts by default, because X charges more for a post with a link; keeping links takes its X links add-on. You don't buy X credits to post through Flaghand, which prepays X's API (what X charges for links).
- One call per plan. A workflow drafts, checks and asks for approval in one request, retried safely with an
Idempotency-Key, and signed notifications tell it what the owner decided.
Pricing and access
Upload-Post's paid plans, billed monthly, are Basic at $24 a month for 5 profiles, Professional at $50 for 25, Advanced at $147 for 75 and Business at $438 for 225. Billed annually they work out to $16, $33, $118 and $350 a month ($192, $400, $1,411 and $4,205 a year). A profile is one person or client, with one account per network, so 5 profiles can hold 5 TikTok and 5 Instagram accounts. Seats grow from one on Basic to ten on Business, and extra profiles are sold as add-ons.
The X links add-on costs $19 a month and allows up to 50 posts with links a month. The free plan needs no credit card, and the pricing section shows a 15-day money-back guarantee.
Flaghand is in early access and public sign-up isn't open yet. This guide doesn't quote a Flaghand price; use Get access to Flaghand for its current entry point.
What you integrate
Upload-Post's API at https://api.upload-post.com takes an Authorization: Apikey header and multipart form
requests: /api/upload for video, /api/upload_photos for photos and /api/upload_text for text, each with a profile
and one or more platform[] values. Leave out scheduled_date and it publishes now; set it, or add_to_queue, to
schedule. Its hosted MCP server at https://mcp.upload-post.com/mcp accepts the same API key or an OAuth sign-in from
Claude.ai and ChatGPT. Webhooks report finished uploads and account connection changes.
Flaghand's live OpenAPI spec describes the same work in a different order:
- From n8n or Make, one
createPostrequest drafts, checks and asks for approval, and returns the owner'sapproval_url, or each draft's problems and fixes. See the exact n8n and Make requests. - An agent can take the steps one at a time: upload media,
createDraft,checkDraft, thenrequestApprovalwith the draft ID and revision. A proposedpost_attime doesn't schedule anything, and a passing check isn't an approval. - Register a signed event receiver to hear when
the owner decides or a job finishes, then read the jobs and use
verifyJobfor the live check.
Agents connect to Flaghand's remote MCP server with a workspace token or OAuth; the agent documentation has the setup for each client.
Who approves each post
Upload-Post's API key publishes, and the pages above don't describe a key that can draft without publishing. Its agent
guides offer approval in the agent framework instead: require_approval: "always" in the OpenAI Agents SDK, or
needsApproval: true in its Vercel AI SDK tools, has the framework ask a person before each publishing call. That
check runs in your agent, so any other holder of the same key can still publish. A read-only calendar link lets a
client look over scheduled posts, but they can't edit, delete or reschedule them there. TikTok's draft mode sends a
post to the account's TikTok drafts to finish in the app, for that network only.
Flaghand also uses a Bearer token, so the difference isn't the authentication header but what the credential can do.
No API token scope can approve, schedule or post. Flaghand's OAuth MCP connectors receive read, drafts, media and
request-approval, not a publishing permission. The owner connects each social account and approves in Flaghand; an
agent or workflow can't do either on their behalf.
What you approve
Flaghand freezes the account, time, text, media, alt text and outgoing request into a snapshot. It hashes that snapshot with SHA-256 and records your passkey signature over the hash. Changing the posting content, account or time needs a new approval, and the scheduler checks the signed snapshot again just before posting. That required step is friction if you want a fully unattended pipeline; it's the point if a person's name is on every post.
After it posts
Flaghand reads each X post back and compares normalized text, author, hidden reply mentions, media count, available alt text, reply chain and quote with the approval. It doesn't verify link destinations or media-file identity, and it has no LinkedIn read-back. Upload-Post reports each upload's status and history, sends webhooks, and offers analytics across networks. Neither a success response nor this limited comparison proves every detail of a post looks right.
TikTok slideshows
Flaghand's slideshow API lets an agent lay out photos and text as slides. One renderer draws it for the preview you approve and for the images TikTok receives, so approval covers the render hash. Flaghand and TikTok explains what posting is available while TikTok reviews Flaghand. Upload-Post posts TikTok videos, photo carousels and slideshows today, directly or as drafts.
Side by side
| Upload-Post | Flaghand | |
|---|---|---|
| Core fit | A posting API for many networks, apps and agencies | A publishing desk for a person and their agents |
| Networks | Twenty-two platforms, including TikTok, Instagram, YouTube and LinkedIn pages | X and LinkedIn personal profiles; TikTok subject to review |
| n8n and Make | Its own n8n node; Make, Zapier and Airtable guides | n8n HTTP Request, Make HTTP module, Zapier Webhooks |
| API and MCP | REST with an Apikey header; hosted MCP with the key or OAuth |
REST with a Bearer workspace token; remote MCP with the token or OAuth |
| Can that credential publish? | Yes | No API token can approve, schedule or post |
| Who approves each post | Optional approval in your agent framework | The owner's passkey over the exact snapshot |
| Links on X | Removed unless you buy the X links add-on | Kept as approved |
| After publication | Status, history, webhooks and analytics | Limited X snapshot read-back; none on LinkedIn |
| Price | Free plan; paid from $24 a month, or $16 billed annually | Early access; public sign-up not open yet |
Try Flaghand
Read Flaghand from n8n, Make, Zapier and GitHub Actions for copyable workflow requests, the agent documentation for the API and MCP contract, and How to let an AI agent post safely for checks to apply to any integration. Get access to Flaghand.