Post notifications
Postly currently sends publish notifications by email. The next release expands that system into Slack, Discord, and Telegram while keeping one consistent payload: publish summary, channel results, action links, and a clear post preview that helps users verify exactly what went live without reopening Postly first.
Release picture
Shipping now
Email is the current notification channel, and the enhancement direction is to keep one shared success payload while expanding delivery destinations.
Coming next
Slack, Discord, and Telegram are planned next, with the post preview kept as the most important part of the notification experience.
Focus areas
Email is live today
Publish notifications are already available through email delivery.
Unified multi-channel roadmap
Slack, Telegram, and Discord are planned without splitting the payload model across different systems.
Preview-first design
The notification should show what was published, not just that something published.
Live now
The current product state is clear: publish notifications are delivered by email today.
Postly currently provides post notifications through email, giving users a direct publish confirmation channel today.
The enhancement work is not just about adding channels. It is about building one consistent notification contract across all of them.
The most important enhancement is that users should be able to see what was published directly in the notification without reopening Postly first.
Coming soon
The roadmap expands delivery channels and makes the post preview a first-class notification object across every supported destination.
The notification system is expanding beyond email so teams can receive publish confirmations in the communication tools they already monitor.
Every notification should include the same essential data so users get a reliable confirmation experience no matter where it arrives.
The roadmap includes recipient preferences, status filtering, retries, deduplication, and notification delivery logging.
How it fits
The current system starts with email and grows into a preview-first, multi-channel notification layer around publish events.
A scheduled publish, manual publish, or multi-channel publish job reaches completion and triggers a notification flow.
The notification payload should contain the publish summary, channel outcomes, and a preview of the content that actually went live.
Email is live today, while Slack, Telegram, and Discord are the next delivery targets for the same core notification data.
Scoped roadmap
These boards capture the enhancement direction clearly so the page stays honest about what exists today and what is planned next.
The post preview is the centerpiece of the enhancement. Users should be able to verify what was published directly from the notification itself.
Why this matters
Faster verification
Users can confirm the published content immediately without opening Postly first.
Less ambiguity after publish
The notification shows what went live, not just that a publish event happened.
What this unlocks
The value is not just another alert channel. It is faster verification, better team visibility, and a stronger post-publish feedback loop.
Users can instantly see what was published and verify that the content looks right.
Publish outcomes can reach teams in the channels they already watch instead of staying trapped in one inbox.
Shared payloads, preferences, and logs make the system more extensible than one-off channel-specific notifications.
Next step
Postly already sends publish notifications via email. The next step expands that into Slack, Discord, and Telegram while keeping the post preview, channel results, and action links consistent everywhere.