Skip to main content Skip to main content
6 platforms · REST API · n8n · MCP · Content Queue | n8n-nodes-postifys postifys-mcp Docs DevHunt
Multi-account publishing · API + n8n + MCP · 7-day trial

Connect client accounts once. Publish with control.

Postifys gives agencies and operators one connected-account layer for supported Facebook, Instagram, YouTube, Pinterest, LinkedIn, and TikTok work—through Dashboard Content Queue, REST API, n8n, or Cursor/Claude-compatible MCP tools.

Start 7-day free trial Read API Documentation

No card required for the 7-day trial. It includes one seat and full publishing access. Add a card to continue; then $4 for the first seat and $2 per additional seat monthly. Platform permissions and content rules still apply.

API-key authentication Idempotency keys Connected-account targeting Publish history
6supported platform workflows
7 daysfree trial, no card required
$4first seat / month after trial (+$2 each extra)
MCPtools for Cursor and Claude
POST /api/instagram/post 
curl -X POST \
  https://postifys.com/api/instagram/post \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Idempotency-Key: workflow-job-123" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "VIDEO",
    "mediaUrls": ["https://cdn.example/video.mp4"],
    "text": "Scheduled from my workflow",
    "instagramAccountId": "CONNECTED_ACCOUNT_ID"
  }'
Quick answer

What does Postifys do?

Postifys is a social publishing service for agencies, operators, developers, and automation teams. Connect supported accounts once, then choose a controlled Dashboard Content Queue, platform-specific REST endpoint, n8n node, or MCP tool while keeping status, history, and retry visibility in one place.

Choose your route

One connected-account layer, four ways to operate

Choose the surface that fits the work. All routes use the same authorized accounts and preserve operational history; platform requirements still determine what can publish.

Dashboard + Content Queue

Create tables, import CSV, assign one job, select destinations, then run, pause, or auto-post after sign-in.

Open Content Queue →

REST API

Use scoped API keys from trusted backend systems and integrate platform-specific publishing calls.

Read API docs →

n8n node

Build visual and scheduled automations with connected-account selectors and credential testing.

Set up n8n →

MCP tools

Use the local postifys-mcp package in Cursor, Claude, or a compatible MCP client.

Set up MCP →
Supported publishing workflows

One integration layer, without pretending every platform is identical

Postifys standardizes authentication and operational tracking while preserving the fields, targets, permissions, and approval requirements of each social network.

Native publishing

Facebook Pages

Publish supported text/link feed posts, native images, and Reels to authorized Facebook Pages. Select a specific connected Page when a user manages more than one.

Native publishing

Instagram Professional

Publish images and Reels to connected professional accounts through Meta’s container and resumable-upload workflows. Personal Instagram accounts are not supported.

Video upload

YouTube Channels

Upload videos with title, description, privacy, tags, category, audience settings, and an optional custom thumbnail to an authorized channel.

Access dependent

Pinterest Boards

Create supported image or video Pins on a selected connected board. Production writes depend on Pinterest granting the required application access.

Member publishing

LinkedIn Members

Publish text, image, video, and link-preview posts to connected member profiles. Company Page publishing requires separate LinkedIn approval and is not currently offered.

Creator review

TikTok Creator Inbox

Upload an eligible video to the connected creator’s TikTok inbox. The creator reviews and completes the post manually; direct public posting needs separate TikTok approval.

Implementation path

From account authorization to publish status in four steps

1

Create a user account

Register, verify the email address, and create a Postifys API key from the secure settings page.

2

Connect social accounts

Complete each platform’s authorization flow. Postifys stores the connection for that user and lists available targets.

3

Send a platform request

Call the matching endpoint with a connected target, supported media URL, and the fields required by that platform.

4

Track the result

Use synchronous responses, asynchronous status polling, publish history, queue state, and failure details to operate reliably.

REST endpoint map

Use the endpoint designed for each destination

All publishing calls require a logged-in session or a Postifys API key. Keep API keys in server-side environment variables or a secrets manager.

Platform Endpoint Primary target Supported workflow
Facebook/api/facebook/postPageFeed, image, Reel
Instagram/api/instagram/postProfessional accountImage, Reel
YouTube/api/youtube/postChannelVideo upload
Pinterest/api/pinterest/postBoardImage Pin, video Pin
LinkedIn/api/linkedin/postMember profileText, image, video, link
TikTok/api/tiktok/postCreator accountVideo upload to inbox
See request fields and examples
MCP for AI agents

Use the same Postifys publishing API from Cursor or Claude

The free postifys-mcp package gives compatible MCP clients tools to list connected accounts, upload media, publish supported posts, poll status, and manage Content Queue. It uses a scoped Postifys API key; your social OAuth tokens stay on Postifys.

Set up Postifys MCP View package on npm

MCP is for agent-driven work. Use the n8n community node for scheduled and visual workflows; both use the same Postifys API.

Cursor / Claude MCP configuration
{
  "command": "npx",
  "args": ["-y", "postifys-mcp"],
  "env": {
    "POSTIFYS_API_KEY": "YOUR_SCOPED_KEY"
  }
}
Built for operations

More than six thin API wrappers

Per-user connections

API keys resolve only the accounts connected by their owner, with target validation before publishing.

Remote media preparation

Queue remote media, inspect it, normalize supported Google Drive links, and serve short-lived files where a platform needs them.

Asynchronous publishing

Accept long-running video work with a submission ID, process it in the background, and query status without holding one HTTP request open.

History and failure reasons

Review recent attempts, platform responses, processing stages, and normalized errors from the dashboard or API.

Retry support

Retry supported failed attempts while preserving their original platform, target, text, and media context.

n8n integration

Use credential testing and dynamic account selectors in the Postifys community node, or call REST endpoints directly.

MCP tools for agents

Use Postifys MCP in Cursor, Claude, or another compatible client to work with connections, media, publishing, and status through the same scoped API key.

Post Data Tables and Jobs

Create a table of post rows, then attach a job with destinations, an interval, and a timezone. Run it now or enable automatic publishing without building an n8n workflow.

Multiple scoped API keys

Create separate masked keys for agencies, n8n, backend services, or clients, with scopes and last-used visibility.

Production safety controls

SSRF protection, restricted CORS, CSRF protection, signed Meta webhooks, masked logs, and required-secret checks.

Connection health UX

See healthy, expiring, expired, and reconnect-required social connections before they interrupt publishing.

Built-in Content Queue

Create post data tables, then run controlled publishing jobs

For repeatable publishing without custom code, sign in to create a Post Data Table, add rows manually or import CSV, and create one job for that table. An entitled publishing account can select connected destinations plus its interval and timezone, then keep it paused, run it once, or enable automatic publishing when the content is ready.

Open Post Data Tables How Create Post works
1

Create table

Add post rows or import a CSV.

2

Create job

Choose accounts, interval, and timezone.

3

Control runs

Run now, pause, or enable auto-post.

Publishing still follows the connected account, platform permissions, and media requirements for every row.

Simple pricing for ads traffic

Start with a 7-day trial, then pay $4 for the first seat, then $2 per extra seat per month

New customers start with a 7-day free trial for 1 seat and full publishing access. No card required. Add a card only to continue after the trial.

  • 1 seat included during trial. Use it to connect your first set of platform accounts and test real workflows.
  • $4 first seat, then +$2 per extra after trial. Add seats only when you need a second account/profile on the same platform.
  • No social reconnect required for billing changes. Subscription and social OAuth connections stay separate.
Trial plan

Postifys API Access

For developers, agencies, n8n builders, and automation teams.

No card required
$0

for 7 days · 1 seat included

After trial$4 for the first seat, then $2 per extra seat per month
API keysScoped keys supported
SupportIn-app Help Center
Start 7-day free trial See full pricing details

Trial starts through Stripe Checkout. Cancel before trial ends to avoid automatic billing.

Clear limitations

What developers should account for before going live

No multi-platform API removes the underlying platform rules. Reliable automation starts with accurate expectations.

Platform review and scopes

Publishing depends on each application’s approved products, scopes, and production access. A successful Postifys connection cannot grant permissions a platform has not approved.

Different content models

Use platform-specific endpoints. Media duration, dimensions, size, privacy, captions, thumbnails, target IDs, and audience controls vary.

Reachable source media

Remote files must be downloadable. Postifys can proxy supported sources, but inaccessible, expired, oversized, or unsupported media will fail validation or platform processing.

Account-type restrictions

Instagram requires a professional account, LinkedIn currently targets members, TikTok Direct Post settings must match creator capabilities, and Pinterest writes depend on approved access.

Common use cases

Where a unified publishing service removes repeated integration work

Automation teams

Connect database, storage, approval, and AI-generation workflows to supported social publishing through n8n.

Agencies and operators

Keep each customer’s connected accounts separate, choose specific targets, and review history from one operational dashboard.

Internal applications

Add publishing to a CMS, asset pipeline, CRM, approval tool, or back-office system without putting social credentials in frontend code.

Retry safe

Idempotency keys

Use stable keys so workflow retries can replay status instead of duplicating posts.

Observable

Status + history

Track queued, processing, published, failed, retrying, and platform failure reasons.

Connection health

Token visibility

See expiring, expired, healthy, and reconnect-required accounts before operations break.

Support

Help tickets

Create support tickets with post IDs, API request IDs, or workflow context from the app.

FAQ

Social publishing API questions

Short answers for developers evaluating Postifys.

It lets an application submit supported posts programmatically instead of publishing manually in every network. Postifys provides one authenticated service while each platform keeps its own permissions and content rules.

Connected Facebook Pages, Instagram professional accounts, YouTube channels, Pinterest boards, LinkedIn member accounts, and TikTok creator accounts. Available operations depend on approval and granted permissions.

Yes. Use the Postifys n8n community node with credential testing and connected-account selectors, or call the REST endpoints from an HTTP Request node. See the n8n integration page.

Yes. Install the free postifys-mcp package with a scoped Postifys API key. It gives compatible MCP clients tools for connections, media upload, publishing, status polling, and Content Queue. Social OAuth tokens remain on Postifys. See MCP setup.

Users authorize their social accounts, create one or more scoped Postifys API keys, and send a key as a Bearer token or X-API-Key header. Store keys only in trusted server-side systems.

New customers start with a 7-day free trial with no card required. The trial includes 1 seat and full publishing access. Add a card to continue; then Postifys is $4 for the first seat and $2 per extra seat per month. Add seats when you need a second account on the same platform.

No. The service and authentication model are unified, but endpoints remain platform-specific because media, caption, privacy, permission, and target requirements differ.

Yes. Approved Direct Post publishes automatically after processing; optional Draft Upload requires creator completion inside TikTok.
Build the first workflow

Start your 7-day trial and publish with verified parameters.

Connect one account, create a scoped API key, send your first request, and use status/history endpoints to keep publishing observable.

Start 7-day free trial Open API Documentation

Continue learning