Zapier social media scheduling: Preflight integration

    Schedule posts to 12 networks from Zapier, in Beta: instant triggers, drafts by default, a rules check inside the Zap and a Publish now that needs confirming.

    Updated · 6 min read · Prices and limits checked against the vendors' own pages and APIs on that date.

    Preflight has a Zapier integration, listed on Zapier with a Beta label, that creates, schedules, queues and publishes social media posts to YouTube, TikTok, Instagram, Facebook, Threads, LinkedIn, Pinterest, Bluesky, Mastodon, Telegram, Discord and Tumblr from any Zap. It starts Zaps too, the moment a post goes live, a post fails or a channel needs signing in again. What sets it apart from a separate Zapier step for each network is the check: a Zap can test a post against every chosen network's publishing rules before it creates anything, and the result is a field the next step can use.

    What you can do with it

    StepKindWhat it does
    Post PublishedInstant triggerA post went live on a channel. Runs once per channel, with the network and the link to the post.
    Post FailedInstant triggerA channel refused a post and Preflight stopped retrying. Runs once per channel, with the reason, the number of attempts and whether a retry can work.
    Channel Needs ReconnectingInstant triggerA channel's sign-in stopped working and Preflight could not renew it, with the channel's name, the reason and a link to reconnect.
    Create PostActionSaves a draft, schedules for a time, adds to each channel's queue, or publishes now.
    Validate PostActionA dry run against every chosen network's rules. Nothing is created.
    Upload MediaActionHands Preflight a public link to a picture or video, which it downloads and measures, and returns the media ID.
    Retry PostActionSends a failed post again, to every failed channel or to one.
    Find PostSearchFinds a post by its ID, with each channel's status, link and error.

    Connect it

    1. Sign in to Preflight and connect your social accounts there. Each network's sign-in has to be done by a person, so it happens in the app and never in a Zap.
    2. Under Settings, then API keys, create a key. Every plan has API access, Free included.
    3. In a Zap, choose Preflight and paste the key. Zapier tests it by reading your channel list, and names the connection by how many channels it found.

    Give the key only the scopes your Zaps need:

    ScopeNeeded for
    posts:readConnecting, the channel list, Find Post and the sample records in the Zap editor
    posts:writeSaving drafts
    posts:publishAnything that goes live: scheduling, queueing, publishing now, Retry Post
    media:read, media:writeUpload Media, and media URLs in a post
    webhooks:writeThe three triggers

    A key without posts:publish can save drafts and never publish anything, which is a sensible start for a Zap you are still trying out.

    Three Zaps to start with

    New blog post to a draft. RSS feed, then Create Post. When stays on its default, Save as a draft, so nothing goes out until a person has read it in Preflight. Map the item's title and link to Text and Link, and the link again to Idempotency Key.

    Content calendar in a sheet. Google Sheets, then Create Post. A new row becomes a post: map the text column to Text, choose At a time under When, map the date column to Scheduled Time, and map the row's ID to Idempotency Key. A row with a date more than five minutes in the past is refused rather than sent late.

    Failed post to Slack. Post Failed, then a Slack message. Map Network, Reason and Post ID into the message. The field Permanent says whether a retry will help, so the person reading it knows whether to press retry or fix the post. Channel Needs Reconnecting deserves the same alert, because every post scheduled to that channel fails until someone connects it again.

    Zapier's Free plan runs two-step Zaps, and multi-step Zaps start at its Professional plan, as its pricing page showed on 2 November 2026. All three above fit in two steps. Adding Validate Post, below, makes three.

    Why validate inside the Zap

    An automation fails where nobody is watching. Most of what makes a post fail is known before it is sent: a caption over a network's limit counted the way that network counts it, a link TikTok will not take, a video outside a network's length or frame-rate range, a YouTube upload without a title, a plan with no publishes left. Validate Post checks these against the rules each network enforces, the same check Preflight's web app runs, and returns:

    • Every Network Accepts It, true or false, for a Filter or Paths step.
    • Errors and Warnings, as counts.
    • Summary, one readable line per problem, such as "Bluesky: Text is 385 characters; Bluesky allows 300." It is worth sending to whoever can fix the post.

    There are two ways to use it. Set Stop the Zap on Errors to Yes and the run halts at that step, with the reasons in the Zap's history. Or leave it on No and let a Filter or Paths step decide on the first field, which also lets one branch send the summary to a person.

    Create Post runs the same checks on the server and refuses a post that would fail when it schedules, queues or publishes. A draft is the exception: it is saved even with a problem, because a person is going to edit it. So a Zap that makes drafts gets real value from a Validate Post step before it, and one that schedules gets the reason earlier and in a form it can act on.

    Safe to run twice

    Zaps get replayed, and a feed can show an item again.

    • Idempotency Key. The same key returns the first post instead of making a second. Map a stable value from the trigger, such as the RSS item's link or the row's ID. Left empty, each run gets a new random key, so a repeated item makes a new post.
    • Publish now has to be confirmed. Choosing Publish now also needs Confirm Publish Now set to Yes, so a test run cannot post by accident. Create Post starts on Save as a draft.
    • No time in the past. A scheduled time up to five minutes old is taken as now, and an older one is refused.
    • Signed deliveries. Turning a Zap on subscribes it to one webhook event and keeps a secret. A delivery that is unsigned, changed or older than five minutes is dropped before it starts the Zap. Turning the Zap off removes the subscription.

    Pictures and video

    Text, Link, Media URLs and Media IDs are the fields a post is built from. Files go in as public https links; Preflight downloads them itself, so nothing passes through Zapier. The kind is read from the file name, so a link with no extension needs Upload Media with Kind set.

    A Zapier step has about thirty seconds in all, and Create Post waits only 15 seconds for a file. For a large video, use Upload Media first, which waits up to 20 seconds and returns a Ready field, then a Delay by Zapier step, then Create Post with the media ID.

    Create Post also has fields for YouTube Title and Privacy, TikTok Privacy, Pinterest Board and First Comment. Any other option goes in Options JSON, keyed by network. The list is in the network options reference.

    What it cannot do

    • Connect accounts. Social accounts are connected in the Preflight app. A Zap uses them once they are there.
    • Take a file directly from an earlier step. Media has to be a public https link. Files uploaded straight from a workflow are something the n8n node and the REST API can do.
    • Retry safely in a blind loop. A Zap from Post Failed straight to Retry Post can go round in a circle when a network keeps refusing the post. Filter on Permanent being false, and expect to check it by hand.
    • Post to X or Reddit. Preflight publishes to the twelve networks listed above.
    • Lift a network's own limits. YouTube's daily upload quota, Instagram's daily publishing cap and TikTok's creator limits still apply. When one stops a post, the reason comes back in plain words.

    Questions people ask

    Does Preflight work with Zapier?
    Yes. Preflight is listed on Zapier with a Beta label, with three instant triggers, four actions and one search. Connect it with an API key from Settings, API keys, and it can create, schedule, queue and publish posts to twelve networks.
    What does Beta mean for the Preflight Zapier integration?
    It is the label Zapier shows on the listing. The integration is public, so anyone with a Preflight account and a Zapier account can use it without an invitation.
    Can a Zap publish a post by accident?
    Create Post starts on Save as a draft, and Publish now also needs Confirm Publish Now set to Yes. A key without the posts:publish scope can only save drafts, whatever the Zap asks for.
    Do I need a paid plan to use Preflight with Zapier?
    Not on Preflight: API keys and webhooks come with every plan, Free included. On Zapier, the Free plan runs two-step Zaps and multi-step Zaps start at Professional, according to its pricing page on 2 November 2026, so a Zap with a Validate Post step needs a paid Zapier plan.
    How do I stop a Zap from posting twice?
    Map a stable value from the trigger, such as an RSS item's link or a row's ID, to the Idempotency Key field of Create Post. Preflight returns the first post for a repeated key instead of creating another. Left empty, each run counts as new.

    Write it once. Let the rules be our problem.

    Preflight checks every post against each network's rules before it leaves, then publishes it to twelve networks. Free plan, no card.