From connecting an account to going live, step by step.
We're not trying to hide what Postju does. Below is what happens from the moment you connect an account to the moment your post appears on the platform — including what we do when something goes wrong.
Connect your accounts
You pick the platform you want to connect from the Channels screen. Postju sends you to that platform's OWN consent page; you enter your password there and it never passes through us. When you grant consent, the platform returns only an access token that can publish on your behalf.
Compose your content
Choose which accounts the post should go to, write the text, and drag in images or a video. The character counter warns you based on the tightest limit among the channels you selected, and tells you right away if you pick a file format that isn't accepted.
Publish now or schedule it
Send it immediately or pick a date and time. Scheduled posts are stored in your own time zone and go live at that exact minute — your browser doesn't need to be open.
Watch the result
You get a separate status for each account: pending, published or failed. A published post keeps its platform link on the card, so you can go check it in one click.
What happens behind the scenes?
For the curious: these are the steps taken while your post is being published.
Each channel is its own job
A post going to five accounts is five independent jobs. When one fails, the others don't wait or get cancelled — which is why you see five separate statuses on the card.
Access tokens are decrypted
Stored permissions are kept encrypted and decrypted only at the moment a post is being published, for that one job. If a token has expired, it's quietly refreshed using the refresh token.
Media is handed to the platform
Some platforms have you upload the image directly; others take a URL and download it themselves. In the second case we generate a signed, short-lived URL for the file that's only valid for that platform's download.
The result is recorded
When the platform accepts the post, the identifier it returns is stored and the post's public link is derived from it. If it refuses, the error message it returned is recorded verbatim — that's the explanation you see on the card.
What happens if a post fails?
We're not claiming errors won't happen. What we're claiming is that we won't hide them from you when they do.
Temporary errors are retried
When a platform reports a short-lived problem (rate limits, timeouts, a transient access error), the post is retried automatically. You don't have to do anything.
Permanent errors are stated plainly
If the text was too long, the file format wasn't accepted, or consent was revoked, retrying won't help. The post is marked failed and the reason is written on the card.
Manual resend
Once you've fixed the problem — shortened the text, swapped the file, reconnected the channel — you resend the post in a single click.
No silent successes
Some platforms accept a request and then drop the content in the background. Wherever we can detect that, we don't call the post 'published' — there's nothing worse than someone searching for a post that was never there.
Trying it beats reading about it.
Connect an account and schedule your first post. If you don't like it, disconnect the channel in one click and delete your account from Settings.
No account yet? You'll create one on the same screen. You can also continue with Google in a single click.