Changelog

Facebook analytics and Instagram inbox are ready

posterly can now turn on Facebook Page analytics and Instagram comment management for production accounts.

Facebook Page analytics

Facebook and Meta connections can now enable Page-level performance in Analytics.

Once a Facebook Page is reconnected, posterly can sync:

• Page followers
• Page views
• Page engagement
• Profile views
• Facebook post interactions

If you want Facebook analytics active, please reconnect your Facebook or Meta account.

Instagram inbox and comments

Instagram direct connections can now use comment management in production.

That powers Instagram comment workflows in Inbox, including:

• Reading comments on recent media
• Replying to comments from posterly
• Hiding or deleting comments when needed
• First-comment support after publishing
• Comment automation rules for moderation and reply workflows

If you want Instagram comments and Inbox active, please reconnect from the Instagram button. Meta-connected Instagram accounts are for Meta/Facebook-linked publishing workflows; Inbox uses the direct Instagram connection.

What to do

Open Connected Accounts, reconnect Facebook or Meta to enable Page analytics, and reconnect from the Instagram button to enable comments and Inbox.

After reconnecting, open Analytics to sync Facebook performance, or Inbox to manage Instagram comments.

Keep your Instagram captions cleaner

You can now add an optional first comment when scheduling Instagram feed posts, Reels, and carousels.

First comments are commonly used for hashtags, extra context, product details, or anything you want close to the post without crowding the main caption. When the Instagram post publishes, posterly posts the comment immediately after it.

How to use it

1. Open the composer
2. Select an Instagram account
3. Write your caption as usual
4. Add your hashtags or extra text in the First comment box on the Instagram tab
5. Schedule or publish the post

The first comment applies to Instagram only. If you are posting to multiple platforms at once, your other captions will not include it.

Where it works

Instagram first comments are available for:

• Feed posts
• Reels
• Carousels

Stories do not use first comments, so the field is disabled when you are scheduling an Instagram Story or Story Series.

Do I need to reconnect Instagram?

New Instagram connections ask for the comment permission automatically.

If your Instagram account was connected before comment management was available, or if a first comment does not appear after a post publishes, reconnect from Connected Accounts:

• Use the Instagram button for direct Instagram connections.
• Use the Meta option if you publish through a Meta-linked Instagram account.

Once the account has the right permission, you can keep using first comments without changing your workflow.

A note on reliability

The post itself stays the priority. If Instagram publishes the post but rejects the first comment, posterly keeps the post marked as published and records the comment issue separately so you can follow up without losing the post.

TikTok slideshows are now supported

You can now create TikTok photo slideshows directly from posterly. Select a TikTok account, upload multiple photos, arrange the order, preview the slideshow, and schedule it with the rest of your content.

When the scheduled time arrives, posterly sends the post to your TikTok inbox. Open the TikTok app, review it, and tap Post. It will not appear publicly until you finish that step in TikTok.

What is included

• Slideshow setup in the composer: upload, crop, remove, and reorder photos before scheduling.
• TikTok preview: step through the slideshow preview before it goes out.
• TikTok details in one place: add a title and disclosure details where needed.
• Inbox handoff: TikTok receives the scheduled post, then you approve it from the TikTok app.
• Image preparation behind the scenes: posterly prepares TikTok-compatible image files at publish time.

What to expect

TikTok photo slideshows are for still images. Videos still use the regular TikTok video workflow.

For now, TikTok requires one final manual approval step in the TikTok app. We will keep improving the flow as TikTok expands Direct Post access.

Why this matters

TikTok slideshows are quick to make, easy to reuse from photo assets, and useful for launches, product roundups, how-tos, recaps, and before-and-after posts. Now you can plan them in the same calendar as everything else.

Try it from the composer by selecting TikTok and uploading two or more photos.

Pinterest video Pins + cover images are now fully supported across posterly:

• Composer: Schedule a single video Pin, extract a frame or upload a custom cover, and keep carousel Pins image-only.
• Public API v1 (/api/v1/posts, create_posts_batch): Pass post_type: "video", a single video media URL, platform_settings.cover_image_url (or video_cover_url), plus the required board_id. Validation now correctly accepts video Pins (single video, no mixing with images or carousels).
• MCP / Agent tools: get_platform_schema("pinterest") now surfaces post_type (image/video/carousel), cover_image_url, and an updated example. The create_post tool description and settings handling include video Pins.
• Platform discovery: GET /api/v1/platforms and the /api-platforms page reflect the complete capabilities.

This brings the dashboard composer, external API, and AI agent interfaces into parity so power users, Zapier-style automations, and MCP agents can schedule video Pins the same way.

How to use (API example)

{
  "account_id": 123,
  "caption": "Check out the new launch video ✨",
  "post_type": "video",
  "media_url": "https://.../launch.mp4",
  "platform_settings": {
    "board_id": "9876543210",
    "title": "Launch video",
    "cover_image_url": "https://.../cover.jpg"
  }
}

Notes:

• Video Pins still require a public, fetchable cover image (JPEG/PNG). The same validation and HEAD checks used in the dashboard apply.
• Carousels remain image-only (2-5 images).
• We continue to use the direct video_url source for simplicity and reliability with Supabase media. The official Pinterest media registration + video_id flow is noted in code for future migration if processing volume grows.
• No new OAuth scopes required: your existing pins:write connection works.

See the updated platform schema docs and call get_platform_schema before building Pinterest automations.

Related: Pinterest analytics & video covers changelog

---

Bonus: As part of the platform API audit, we also published a detailed implementation plan for Bluesky video support (3-minute clips, proper app.bsky.embed.video + video.bsky.app processing flow). The plan is tracked in docs/planning/bluesky-video-support.md and will be executed on a follow-up branch once Pinterest ships. Bluesky remains the last production platform without native video, coming soon!

API v1 is now a real automation surface

We expanded posterly API v1 beyond basic scheduling so agencies, internal tools, and AI agents can inspect capabilities before they act.

What is new

• GET /api/v1/platforms returns supported platforms, settings, media limits, helper tools, analytics support, and planned integrations.
• GET /api/v1/accounts/{id}/schema gives account-specific settings guidance.
• POST /api/v1/platforms/trigger exposes helper actions such as Pinterest boards, YouTube playlists, TikTok creator info, LinkedIn mentions, and X quota checks.
• POST /api/v1/media/upload-from-url fetches remote media safely with SSRF and size checks.
• GET /api/v1/connect and GET /api/v1/connect/{platform} help external workflows guide users into the right connection flow.
• DELETE /api/v1/accounts/{id} disconnects accounts with the same cleanup path used in the dashboard.

Post lifecycle and repair

The API can now support more operational workflows:

• PUT /api/v1/posts/{id}/status pauses, resumes, schedules, or returns posts to draft.
• GET /api/v1/posts/{id}/missing explains what still needs to be fixed before publishing.
• PUT /api/v1/posts/{id}/release-id repairs external release/group metadata.
• DELETE /api/v1/posts/group/{group} cleans up grouped draft, scheduled, failed, or paused posts.

See the REST API docs and the API reference for the full shape.

Google Business is now automation-ready

Teams can now run common Google Business Profile review workflows through the public API, MCP, WebMCP, and CLI.

What is available

• List reviews with rating and unanswered filters.
• Generate the public Google review link for a location.
• Run a live local-profile audit with practical recommendations.
• Generate brand-aware AI reply suggestions before posting.
• Post or delete owner replies after explicit confirmation.

These workflows are useful for local businesses, franchises, agencies, and support teams that need repeatable review operations without scraping the dashboard.

The CLI includes:

posterly gbp:reviews --account-id 123 --unanswered --pretty
posterly gbp:review-link 123 --pretty
posterly gbp:audit 123 --pretty
posterly gbp:suggest-reply --account-id 123 --star-rating 5 --review-text "Great service" --pretty
posterly gbp:reply --account-id 123 --review-name accounts/123/locations/456/reviews/abc --comment "Thanks Alex. Glad we could help." --confirm --pretty

The MCP server is now a full agent surface

posterly-mcp-server@0.19.0 expands the MCP package to 49 tools and aligns the HTTP and stdio transports around the same capabilities.

Highlights

• Platform discovery with list_platforms, get_platform_schema, and trigger_platform_helper.
• Safer posting tools for create, batch create, update, status changes, missing-content checks, release IDs, and group cleanup.
• Media upload tools, including signed uploads and upload-from-url.
• Analytics, activity, and webhook tools for unattended workflows.
• Video generation discovery, cost estimation, generation, and job polling.
• Google Business Profile reviews, review links, profile audits, AI reply suggestions, and reply management.
• OAuth developer client management for public PKCE apps.

The MCP server card at /.well-known/mcp/server-card.json now derives its tool list from the same source as the HTTP MCP implementation, reducing drift between docs, discovery, and runtime.

Upgrade with:

npm install -g posterly-mcp-server@latest

or keep using:

npx posterly-mcp-server

A developer platform layer is taking shape

posterly now supports self-serve public OAuth + PKCE developer clients for apps that need to act on behalf of a posterly user.

OAuth client management

New API endpoints:

• GET /api/v1/oauth/clients
• POST /api/v1/oauth/clients
• PATCH /api/v1/oauth/clients/{clientId}
• DELETE /api/v1/oauth/clients/{clientId}

Developer clients are user-owned, public PKCE clients. Redirect URIs are exact-match only, HTTPS is required except localhost, and client secrets are intentionally not part of this first pass.

CLI preview

The new posterly CLI package includes PAT auth, browser OAuth login, JSON output by default, and commands for accounts, posts, platforms, media, analytics, activity, webhooks, video, Google Business, and OAuth clients.

Example:

npx @posterly/cli@latest auth:login
npx @posterly/cli@latest whoami --pretty
npx @posterly/cli@latest platforms:schema --platform pinterest --pretty
npx @posterly/cli@latest posts:create --account-id 123 --caption "Launching soon"
npx @posterly/cli@latest oauth:create-client --client-name "Agency approval app" --redirect-uri https://agency.example.com/oauth/callback --scopes accounts:read,posts:read,posts:write --pretty

Use npx for the no-install flow. A global posterly command is available only after npm i -g @posterly/cli@latest succeeds.

The CLI is intended for local automation, CI scripts, agency workflows, and developers building on top of posterly.

Better automation needs better feedback loops

The public API now includes webhook and activity primitives so external systems can react to publishing outcomes without polling the dashboard.

New endpoints

• GET /api/v1/activity
• GET /api/v1/notifications
• GET /api/v1/webhooks
• POST /api/v1/webhooks
• PATCH /api/v1/webhooks/{id}
• DELETE /api/v1/webhooks/{id}
• POST /api/v1/webhooks/{id}/test

Webhook deliveries are signed with X-posterly-Signature using a timestamped HMAC format.

Supported events

• webhook.test
• post.created
• post.updated
• post.deleted
• post.publishing
• post.published
• post.failed
• account.disconnected
• analytics.synced

This is the foundation for Make, n8n, internal reporting, Slack alerts, client-review workflows, and AI agents that need to know what happened after scheduling.

What's new

Instagram's Trial Reels format lets you publish a Reel to non-followers first, gauge how it performs with a fresh audience, then decide whether to share it with your existing followers. posterly now supports scheduling Trial Reels directly from the composer, with full parity in the API and MCP.

How to use it

1. Open the composer and select your Instagram account
2. Upload a video and switch the post type to Reel
3. In the Instagram options, toggle Trial Reel on
4. Optionally turn on Auto-share if it performs well to let Meta share the Reel with followers automatically if Instagram decides it's performing
5. Schedule or publish as normal

API and MCP

Trial Reels are part of the v1 API and MCP post-settings payload:

{
  "settings": {
    "post_type": "reel",
    "is_trial_reel": true,
    "graduation_strategy": "MANUAL"
  }
}

graduation_strategy defaults to "MANUAL" (you decide later inside Instagram). Set "SS_PERFORMANCE" to let Meta auto-share with followers if the Reel performs well.

Important: check account eligibility first

Meta controls which Instagram accounts can publish Trial Reels. posterly can send the Trial request through the Graph API, but it can't activate the feature for an account.

Before relying on Trial Reels here, open the Instagram app for that account, create a Reel manually, and check the final sharing screen. If the Trial toggle appears there, the account should be eligible. If it doesn't appear in Instagram, Meta will likely reject the post when posterly publishes it.

Notes

• Trial Reels are Reel-only. They are not available on feed, carousel, or story posts.
• Collaborators are not sent on Trial Reels. Instagram does not allow Collabs for this format.
• If Meta rejects the Trial Reel, the post fails and can be rescheduled as a normal Reel.

See the full Instagram Trial Reels guide for the composer workflow and eligibility check.

Split one image into reusable transparent assets

AI Image Splitter is now live in the Media Library and Composer.

Upload a screenshot, collage, or source image, draw boxes around the objects you want, and posterly generates each selection as a separate transparent PNG asset in your Media Library.

What is new

• Draw-to-select extraction for quickly marking the parts of an image you want to turn into assets
• Batch generation so one source image can become several reusable media-library items
• Transparent PNG output designed for reuse in posts, carousels, thumbnails, and designs
• Media Library integration so generated assets appear alongside your AI images, uploads, videos, and folders
• Composer access for creating splitter assets while building a post
• Selection management with naming, editing, resetting, and generated-result download controls

Why it matters

Useful creative material often starts life inside a bigger image: a product photo in a collage, a client logo on a screenshot, a person inside a training shot, or a prop you want to reuse later.

Instead of cropping manually and then fighting with background removal tools, you can now select the region once and let posterly create clean assets that are ready to reuse.

How to use it

1. Go to Media Library or open the media tools in Composer
2. Choose AI Image Splitter
3. Upload the source image
4. Draw one or more boxes around the assets you want
5. Add optional direction, such as preserving label text or keeping object shadows
6. Generate the assets and use them from your Media Library

This is especially useful for turning raw brand, gym, product, event, and behind-the-scenes images into reusable creative building blocks.

Your media library is now easier to organize

The Media Library has grown from a place to browse generated assets into a proper workspace for managing reusable content.

You can now group media into folders, move several assets at once, and use right-click actions to work faster without opening each item individually.

What is new

• Folders for organizing images and videos by campaign, client, content batch, or approval status
• Multi-select so you can select several assets and add them to a folder in one move
• Drag-and-drop into folders for a more natural asset-management workflow
• Right-click actions on media cards, including copy URL, download, add to composer, resize with AI, edit image, animate with Veo, open in a new tab, and edit in Design Studio
• Folder-safe removal so taking an item out of a folder does not delete the underlying media file
• Cleaner header with the noisy top-right item count removed

Why it matters

If you create a lot of content in posterly, the hard part is not just generating the asset. It is finding the right one again, grouping approved content, and getting it into the next workflow quickly.

Folders make the Media Library feel more like an asset manager: create a folder for a campaign, add approved images and videos, then keep building that collection over time.

How to use it

1. Go to Media Library
2. Create a folder for a campaign, client, or approved content batch
3. Select one or more media cards
4. Add them from the bulk folder control, right-click menu, or drag them onto a folder
5. Right-click any single asset when you want to send it to Composer, Veo, Design Studio, or download it

This is a small interface upgrade with a big workflow payoff: fewer clicks, less hunting, and cleaner approved-content organization.

Pinterest is now a fuller part of posterly

Pinterest publishing already worked in posterly. This update makes it much more useful after the post goes live, and gives video Pins better control before they publish.

What is new

• Pinterest analytics in the Analytics dashboard with account-level trends, top Pins, content mix, and best-time reporting.
• Pin-level performance metrics including impressions, saves, outbound clicks, Pin clicks, and engagement.
• Pinterest spreadsheet exports so you can review daily and monthly performance alongside Instagram, LinkedIn, and Google Business.
• Custom video Pin covers in the composer. Upload a JPEG/PNG cover or capture a frame from the video before scheduling.
• Pinterest cover validation before publishing so oversized, unreachable, or unsupported cover images fail clearly instead of disappearing silently.
• Pinterest analytics in the API and MCP server through get_account_analytics and get_post_analytics.

Why it helps

Pinterest is often a long-tail traffic channel, so the useful question is not just "did this post publish?" It is "which Pins are still earning impressions and outbound clicks over time?"

With this release you can:

• Compare Pinterest growth and engagement without leaving posterly.
• Spot Pins that drive traffic, not just saves.
• Pull Pinterest performance into AI assistant workflows through MCP.
• Give video Pins a polished, intentional cover instead of relying on a random frame.
• Export Pinterest numbers for client reports or spreadsheet review.

Account scopes

Pinterest analytics uses the read scopes already requested by the posterly Pinterest connection: boards:read, pins:read, and user_accounts:read.

If your Pinterest account was connected before this analytics rollout, reconnecting it is still the cleanest way to make sure all granted scopes and account metadata are refreshed.

MCP update

posterly-mcp-server@0.8.1 includes the Pinterest analytics updates.

Upgrade with:

npm install -g posterly-mcp-server@latest

or keep using:

npx posterly-mcp-server

YouTube analytics now lives inside posterly

You can now track YouTube channel and video performance in posterly Analytics, alongside Instagram, LinkedIn Company Pages, Google Business, and Pinterest.

This is focused on organic performance: views, watch time, subscribers, likes, comments, shares, and top videos. Revenue and other monetary analytics are intentionally out of scope.

What is live

• YouTube channel analytics with subscribers, views, watch time, average view duration, likes, comments, and shares.
• Top YouTube videos ranked by views, engagement, likes, comments, shares, watch time, or average view duration.
• Video thumbnails and titles pulled from YouTube so performance rows are easier to recognize.
• Daily trend charts for views and watch-time minutes.
• Spreadsheet exports for YouTube subscribers, views, watch minutes, and subscriber movement.
• REST API and MCP support through get_account_analytics and get_post_analytics.

Why it helps

YouTube performance is often a mix of reach and depth. A video can have fewer views but stronger watch time, or a lot of reach but weaker retention.

With this release you can:

• Review YouTube performance without leaving posterly.
• Compare channel growth and video performance alongside other platforms.
• Pull YouTube analytics into assistant workflows through the MCP server.
• Export watch-time and subscriber history for client reports.
• Reconnect older YouTube accounts once to unlock the new analytics scope.

Account scopes

YouTube analytics uses:

• youtube.upload for publishing
• youtube.readonly for channel and video metadata
• yt-analytics.readonly for channel and video analytics

Existing YouTube connections need to be reconnected once so Google can grant the new yt-analytics.readonly scope. This is a non-sensitive scope and does not include revenue metrics.

The Google Cloud project also needs the YouTube Analytics API enabled, in addition to the existing YouTube Data API used for publishing and metadata.

MCP update

posterly-mcp-server@0.10.0 includes the YouTube analytics updates and the expanded API/MCP schema tools.

Upgrade with:

npm install -g posterly-mcp-server@latest

or keep using:

npx posterly-mcp-server