Zapier

Connect FoPost scheduling and publishing to everything else in your Zapier account.

The official FoPost integration for Zapier connects scheduling and publishing to the rest of your Zapier account: draft a post when a row lands in a sheet, publish when a deal closes, alert the team the moment a delivery fails.

It is a Zapier CLI platform app, not a package. There is no registry coordinate and nothing to install locally; the artifact is pushed to the Zapier platform.

This is a 0.x release. Triggers, actions, and their fields are still settling and a minor version may change them.

Source and issues: github.com/fopost/fopost-zapier. MIT licensed.

Install

The integration is a private Zapier app today, which means it works but is not searchable in the Zap editor. Open the invite link and the FoPost triggers and actions appear in your account straight away:

https://zapier.com/developer/public-invite/245788/97efdb1a56eae2dbebd9a79b0ecca1d0/

Listing it in the public App Directory is a separate step: Zapier requires at least three accounts running live Zaps before it will review an integration for the directory.

You do not need to wait for the public listing. Anyone with a Zapier account can run it privately:

git clone https://github.com/fopost/fopost-zapier.git
cd fopost-zapier
npm install

npx zapier-platform login      # once, with your Zapier account
npx zapier-platform register   # once, creates the app
npx zapier-platform push       # builds and uploads a version

push prints an invite link. Open it, connect your FoPost API key, and the triggers and actions show up in the Zap editor. Anyone you share that link with can use the same private version.

Connect

The integration authenticates with a FoPost API key, sent as an X-API-Key header. Create one at Settings → API Keys in the dashboard with the workspaces, accounts, posts, and labels scopes, so every trigger and action works.

Zapier stores the key as a password field and scrubs it from logs, and it is only ever sent to the FoPost API.

A 401 is surfaced as an expired connection, so Zapier asks you to reconnect rather than failing the Zap silently. A 402 carries the upgrade link, and a 429 backs off for as long as the API asks.

Triggers

Trigger	Fires when
New Published Post	FoPost finishes publishing a post. Filterable by workspace and label
Post Failed to Publish	A post fails to reach one of its accounts. One event per failed account, with the platform error
New Connected Account	A social account is connected to a workspace

Actions

Action	Does
Create Post	Creates a draft or scheduled post for one or more connected accounts, with media, labels, and a title
Publish Post	Queues an existing draft or scheduled post for delivery
Upload Media	Uploads a file from an earlier Zap step and returns a URL for Create Post
Add Label	Creates a label in a workspace

Searches

Search	Finds
Find Post	One post by id, or the newest post matching a text or status search
Find Account	A connected account by username, platform, or workspace

How publishing works

Creating and publishing are two steps. Create Post stores a draft, or a scheduled post that FoPost publishes for you at its time. Publish Post hands a draft to the delivery queue and returns as soon as delivery is queued, not once the post is live.

Use the New Published Post or Post Failed to Publish trigger to learn the outcome.

Workspace, account, and label fields are live dropdowns, and the account and label lists narrow to the workspace you pick.

MakeThe official FoPost app for Make, with polling and instant triggers, actions, and searches.n8nThe official n8n community node for FoPost, with a signature-verified trigger.API ReferenceBase URL, envelopes, pagination, and errors for the FoPost REST API.