Docs·Automation

Scheduling & publishing

How connections work, what platforms are supported, and how the scheduler fires posts.

Updated 2026-07-22

Scheduling and publishing are handled by a single integration under the hood — one connection per platform, and Postazo talks to each platform through that connection. This page covers what platforms are supported, how to connect, and how the scheduler decides when to fire.

Supported platforms

  • Facebook — page-level posting.
  • Instagram — feed, Reels, Stories, carousels.
  • TikTok — video only.
  • LinkedIn — personal and page.
  • X (Twitter) — text, images, threads.
  • YouTube — Shorts.
  • Pinterest — pins.
  • WordPress — for source ingestion (blog posts pulled into the generator) plus publishing text posts as blog articles.

The exact set available depends on your account tier — see the Billing page for what's included.

Connecting an account

Open the Brand KitConnections tab. Each platform has a card with a Connect button.

  • Most platforms use OAuth. Click Connect, sign in on their side, approve, land back on Postazo.
  • Some (WordPress in particular) use a URL-encoded OAuth flow with quirks. Follow the on-screen instructions.
  • Once connected, the card shows the connected account name and a Disconnect button.

Connections are per-project. Different projects can point at different accounts on the same platform.

Scheduling a post

Two ways posts get scheduled:

  • From Create — after generation, click Schedule and pick a date + time in your local timezone.
  • From Autopilot — a Schedule node in a workflow computes the timing from the trigger.

Scheduled posts show up in Scheduled with a clear list of what's queued, per destination.

When posts actually fire

The scheduler polls every minute. When a scheduled slot's time is reached:

  1. The post is handed to Post For Me (our publisher).
  2. Post For Me pushes to each destination platform.
  3. Delivery status updates back into Postazo per-destination — Delivered, Pending, or Failed.

You'll see the final status in Posts within about 30–90 seconds of the scheduled time.

Failure handling

If a destination fails:

  • The failure is logged with the platform's error message on the Post detail page.
  • Other destinations for the same post are unaffected.
  • Common failures: expired token (reconnect the account), platform rate limit (retry later), media too large (recompose).

Posts don't retry automatically on failure — that's deliberate, because most delivery failures are auth or content issues that need your input.

Cancelling a scheduled post

Open Scheduled, click the post, click Cancel. Cancellation is instant — the post never fires.

You can also Edit a scheduled post: changing copy, changing destinations, changing scheduled time. Edits carry through to the queued fire — same post row, updated content.

Publishing directly to the app

For text posts (LinkedIn, X), you can also publish immediately from Create with Post now. Same pipeline, no scheduler in between — the post fires within seconds.