Answer: Reconnect the affected social account in Postifys, confirm connections list health, then retry the failed history item. Rotate the Postifys API key only if it was exposed.
What this means in a real publishing workflow
An expired access token is normally refreshed from a stored refresh token. Reconnection is required when the refresh token is missing, revoked, belongs to a different app, or no longer grants access to the selected destination.
Recommended implementation
- Read the platform and error code in Post History.
- Refresh the connection list to confirm the account still appears.
- Reconnect only the affected platform account.
- Retry the failed post after the new connection is visible.
How to verify the fix
Rotating a Postifys API key does not repair a platform OAuth token; they serve different purposes. Never paste platform access tokens into workflow fields or support messages.
Operational check: Test with one item, confirm the final destination and Postifys history state, and only then enable the recurring workflow. Keep the returned Postifys ID beside the source row so every result remains traceable.
Related Postifys resources
API documentation · Error reference · n8n automation guide · Safe retry guide · Compatibility matrix