
Social Channels
The Social Channels view uses a control-panel layout rather than a long settings form. Platform tiles are real selectors. Their visual state comes from the current workspace connection records:- A connected/healthy channel shows an active state.
- A connection that needs reauthorization shows an attention state.
- An unconnected channel offers the appropriate connection path when available.
What you can do from a channel
Available actions depend on the selected platform, connection health, plan, and account capabilities. Typical actions include:- Connect a supported account.
- Inspect the connected identity.
- Open account management details.
- Reconnect an unhealthy authorization.
- Open the Composer with an eligible account selected.
- Review an upgrade or onboarding requirement when publishing is not currently available.
- Disconnect the account after reviewing the impact.
Publishing access by plan
Connecting an account and publishing to it are separate checks.
Connected-account capacity is currently 5 on Free, 12 on Starter, and 30 on Pro. Enterprise capacity is configured for the customer. Publishing availability remains a separate entitlement and rollout check.
WhatsApp is an Agent access surface on eligible plans, not a standard direct social publishing destination. Telegram remains supported for eligible or existing connections but is intentionally not promoted as a primary tile in the current Social Channels presentation.
Connect an account
1
Choose a channel
Open Connections → Social Channels and select the platform you want to connect.
2
Start the connection
Use the connection action shown for that platform.
3
Authorize Socializioz
Complete the provider authorization flow and approve the permissions required for the capabilities you intend to use.
4
Choose the correct identity
When the provider supports multiple Pages, professional profiles, channels, or accounts, choose the intended destination.
5
Verify the result
Return to Connections and confirm the correct account identity and healthy connection state.
Connection details
The account management surface can show useful connection context such as:- Provider/account identity.
- Profile name or handle.
- Current health.
- Available authorization/capability information.
- Reconnect or disconnect actions.
- Create/open actions supported for that account.
Connection health
A connected account can have different effective capabilities depending on its token, account type, granted permissions, plan, and provider rules.
A healthy connection does not guarantee that analytics, comments, inbox, or every publishing format is available. Those are separate capabilities.
Reconnect safely
When a channel needs attention:- Open the affected account.
- Choose Reconnect.
- Complete the provider authorization flow again.
- Confirm that Socializioz returns to the same intended workspace/account identity.
- Verify the connection is healthy before retrying scheduled or failed publishing work.
Disconnect an account
Disconnecting removes or disables that active Socializioz connection; it does not delete content already published on the social platform. To revoke authorization completely at the provider level, use the provider’s own authorized-app/business-integration controls when necessary.Connected apps and data
The public Connectors catalog extends Socializioz beyond social publishing channels. The current available Agent-capable managed connector baseline includes services across several groups:- Files and content: Google Drive, Google Docs, Dropbox, OneDrive, Notion.
- Communication and work: Gmail, Slack, Microsoft Teams, Google Tasks, Airtable.
- Analytics and advertising data: Google Analytics, Google Ads, TikTok Ads, Pinterest Ads, Reddit Ads.
- CRM, sales, and marketing operations: HubSpot, Salesforce, Apollo, Omnisend.
- Community and video data: Reddit and YouTube.
How Agent execution works
For managed connected apps:- Supported read, search, and reporting actions can execute directly.
- Supported write actions do not execute silently. Chat returns a confirmation card and the user must choose Approve & run before Socializioz issues the one-time confirmation and executes the action.
- Destructive generic actions are blocked rather than being treated as ordinary Agent actions.
- Social publishing, including YouTube publishing, remains on the canonical Socializioz Post lifecycle with its normal workspace, plan, media, approval, scheduling, and publishing checks.
