Verify, renew and disconnect social accounts
Check the actual destination identity, understand token maintenance and remove local credentials when a connection should no longer be used.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Where to start
Social accounts → Verify connection / Check all connections / Disconnect
PermissionManage connections
Before you begin
Verify the connected account identity before using it for a campaign or handover. A healthy token does not guarantee the next post will satisfy every content rule.
Follow these steps
- Open Social accounts and choose Verify connection for the intended destination. Read the reported identity or error.
- Use Check all connections to review a batch through the interface; allow it to check each connection rather than repeatedly starting the batch.
- For an expired, revoked or identity-changed connection, correct the provider account and reconnect through its official flow.
- When removing access, choose Disconnect for the exact destination and confirm.
- If the organisation also needs to revoke the external grant, remove the app through the provider’s account/security controls.
Fields and options
- Verification
- Queries the provider and checks the returned identity against the stored destination.
- Maintenance
- The normal CRM cron checks due connection health and renews supported expiring credentials where the provider allows it.
- Disconnect
- Clears the local connection tokens and prevents its queued work from using that connection.
Rules and limits
- Disconnecting locally is not the same as revoking an OAuth grant at the provider.
- Not every provider issues a renewable refresh token; reconnect when renewal is unavailable or access was revoked.
- Changed account identity is not silently accepted as the same destination.
Check the result
- Read the latest verification result and compare its identity with the intended account.
- After disconnecting, confirm the destination is unavailable for new publication.
If something does not look right
- A transient provider outage does not justify repeatedly reconnecting or duplicating posts.
- If maintenance is not advancing, check the workspace’s normal cron and module activation before investigating individual tokens.
Common questions
Does Check all connections publish anything?
No. It verifies account connections.
Will the module renew every provider forever?
No. Renewal depends on provider token support, continuing permission and app policy; some connections need explicit reauthorisation.