Does my channel connection expire?
It renews itself automatically every 15 minutes, well before the old token would expire. You only hear from us if a renewal fails.
Published Aug 31, 2026
1. A check every 15 minutes, not on demand
A background sweep looks for any connection whose token is about to expire and renews it ahead of time, rather than at the moment you try to publish, when a stale token would cost you a failed post.
2. You don't hear about it when it works
A successful renewal doesn't email you or show up anywhere. The connection keeps working, and there's nothing for you to check.
3. An email only when a renewal fails
If the renewal itself is rejected, because the account owner revoked access for instance, that's the one case you're notified, with a direct link to reconnect. See how you find out when a channel disconnects for what that notification looks like.
More guides
How to connect PostEase to Zapier or Make
Every publish can POST a signed payload to a Zapier Catch Hook or a Make custom webhook, carrying the caption, the account and a link to the live post. No app listing needed, and you can send a test event to map the fields.
Connecting PostEase to the rest of your stack
The outbound webhook, Zapier and Make, importing a calendar from another scheduler, and the browser extension are one integration surface, not four separate things to discover on your own.
Adding alt text to the images you schedule
One field in the composer, sent to X, LinkedIn, Pinterest, and Bluesky with the image. What it is for, what the 500-character cap comes from, and why video is left out.
How to set your workspace timezone
Every time you see or type in PostEase is in one zone chosen for the workspace, not your browser’s. Posts already scheduled keep their exact time when you change it.
Connect once. Let the renewal happen in the background.
Every channel you have, included. Adding another does not change the price.