Some networks have no publishing API. Schedule them anyway.
Substack and its neighbours never opened a write API, so no tool can post there for you without holding your password. FoPost Publisher takes the other route: it fetches what you scheduled, hands you the title, body, and image on your clipboard, and you paste and publish. Your account stays yours.
Your queue in the toolbar. Copy, paste, mark done.
Real shape of the popup: what you scheduled, what is due right now, a copy button for each part of the post, and the two buttons that close the loop back to FoPost.
- SubstackDue now
Most launches die on Tuesday
The people who would have shared your launch are still catching up on their inbox. Here is what to do instead, with five examples from last quarter.
Copy titleCopy bodyCopy imageMark publishedSkipOpen Substack - SubstackThu, Aug 14 · 9:00am
What we shipped in July
Five things went out, one came back off the roadmap. The short version, plus the reasoning on the one we cut.
Copy titleCopy body
You plan the month, then remember Substack is not in it.
Every other network sits in one calendar. The one with no API sits in your head, which is why it goes out three days late or not at all.
The tools that do post there ask for your login and drive the site with a script. One layout change and your post is mangled, or your account is flagged for automation.
So you do it by hand: open FoPost, find the draft, copy the title, tab over, paste, go back for the body, go back again for the image. Four round trips per post.
Is the extension for you?
For you if
- You publish to Substack or another network with no write API, alongside the ones FoPost posts to directly
- You want one calendar for everything, even the parts you send by hand
- You would rather paste a post yourself than hand any tool your login
- You keep forgetting the manual send until two days after you planned it
Not for you if
- Every network you use has a publishing API. FoPost already posts to those for you, so there is nothing here to install.
- You want the manual network fully automated. That means handing over your password and driving the site with a script, which is exactly what this avoids.
- You work only on a phone. Browser extensions are a desktop thing.
The manual step, minus the round trips.
This is deliberately a small tool. It gets your scheduled content onto your clipboard and gets the status back into FoPost, and it touches nothing else.
Your queue, in the toolbar
Open the popup and the content you scheduled for manual networks is already there: platform, scheduled time, title, body, and image. No hunting through the dashboard for the draft.
One click per piece
Copy title, copy body, copy image. The image goes to the clipboard as an image, so it pastes straight into the editor. If the browser refuses the binary copy, you get the URL instead rather than nothing.
It tells you when something is due
The extension checks your queue every five minutes in the background. Anything due puts a count on the toolbar icon and fires a notification, so a scheduled send does not depend on you remembering.
The status goes back to FoPost
Hit Mark published once the post is live, or Skip if you decided against it. Either way the item leaves the queue and your dashboard shows the real state instead of a permanent "pending".
A scoped key, not your password
You paste one FoPost API key into the options page, scoped to the extension and nothing more. Your social accounts are never touched, because the extension has no access to them.
It cannot read the sites you visit
The extension asks for permission to reach the FoPost API and no other host. It has no access to substack.com or any site you browse, so there is no page reading, no DOM automation, and nothing to audit on that front.
Install. Connect. Copy and paste.
Install it
The extension is in beta and not in the Chrome Web Store yet. Download the build and load it through your browser's developer-mode extension page. Chrome and other Chromium browsers today.
Paste your API key
Create an FoPost API key with the extension scope, paste it into the options page, done. That key is the only credential involved, and it reaches nothing but the FoPost API.
Schedule as normal
Compose in FoPost and schedule to a manual network the same way you schedule anything else. It goes to a waiting state instead of a publish queue, and the extension picks it up.
Paste and mark it done
When something is due you get a badge and a notification. Open the popup, copy the title, body, and image, paste them into the network, publish, then hit Mark published so FoPost knows it landed.
Three ways to post where there is no API.
One of them costs you your password, one costs you four tab switches a post, and one is this.
Tools that log in as you
What "full automation" actually means
- You hand over your username and password, or a session cookie.
- A script drives the site. One layout change and the post ships mangled.
- Most networks treat scripted logins as a reason to lock the account.
- If the tool is breached, your account goes with it.
Doing it by hand from the dashboard
What careful founders do today
- Open FoPost, find the draft, copy the title, tab over, paste.
- Go back for the body. Go back again for the image.
- Nothing reminds you when the scheduled time passes.
- The dashboard still shows it as pending, because nothing told it otherwise.
FoPost Publisher
What you actually want
- Your queue in the toolbar. One click per title, body, or image.
- A badge and a notification when something is due.
- Mark published and the dashboard reflects reality.
- No password shared, no script driving the site, no host access.
Publishes to all major networks
Frequently asked questions
Where do I get it?
Which browsers are supported?
Which networks does it cover?
Can it read the pages I visit?
Does it need my Substack login?
What happens if I never mark a post published?
How does the image copy work?
Does it cost extra?
What about a mobile app?
Ready to try browser extension?
7-day free trial. 30 platforms. Unlimited posts on every plan.