Connect Social Accounts and Destinations
Connected destinations are the foundation of everything else in Postly. If the right channels, pages, and targets are not connected cleanly, scheduling and analytics will never feel dependable.
What Postly connects
Depending on the platform and plan, a workspace can connect:
- social accounts
- child pages or channels under a parent account
- newsletter or email publishing targets
- audience groups for faster routing
Postly uses official platform connections so access remains compliant and easier to maintain over time.
Recommended setup pattern
- Decide which workspace should own the destination.
- Connect the parent account through the official authorization flow.
- Select the specific pages, channels, or downstream targets that matter.
- Confirm the right operator or team can see them.
- Test with a simple draft before scheduling a full campaign.
Common structure mistakes
Connecting everything into one workspace
This creates avoidable clutter and approval confusion. Keep clients, brands, or business units separated where possible.
Forgetting child pages
Some platforms expose additional pages or channels after the parent account is connected. Make sure the actual publishing target is connected, not just the parent identity.
Assuming every channel behaves the same
Even when the connection is healthy, platform rules still differ. Use Postly validation and previews before a large campaign.
For developers and automations
In API and MCP flows, you should resolve the workspace first, then fetch connected targets before creating a post. That is the safest way to avoid publishing to the wrong destination.