Connecting your platforms (and fixing a broken connection)
You schedule a week of posts, go on with your life, and find out on Friday that the connection expired on Monday and nothing went out. Silent failure is the worst kind. Connections are made once per platform per project. When one breaks, Forgefy tells you before you schedule rather than after your post fails.
Step 1: Open Settings and go to the platform connections.
Open Settings and go to the platform connections.
Step 2: Connect each platform you want to publish to and complete the provider's author…
Connect each platform you want to publish to and complete the provider's authorisation.
Step 3: If a platform shows as disconnected, reconnect it from the same place.
If a platform shows as disconnected, reconnect it from the same place.
Step 4: Reschedule anything that failed while it was down.
Reschedule anything that failed while it was down.
Good to know
You get a warning toast when you try to schedule to a platform whose account is not connected. It does not wait until publish time to tell you. When a platform has an account-level problem, that whole platform is paused rather than hammering the API with every queued post. One probe per cycle checks whether it has recovered. Connections are per project, so switching project never carries the previous project's accounts or platform selection with it.
Why did a post fail with a platform error?
Technical failures retry briefly and then stop. Account-level problems, like an expired token, pause the platform and need a reconnect from you.
Can two projects post to the same account?
Yes, but connect it in each project so the mapping stays explicit.
Related