Home / Guides / Meta Publishing Permissions and Token Refresh

Meta Publishing Permissions and Token Refresh

How Meta Page and Instagram permissions affect Postifys publishing and what to do when tokens expire or reconnect is required.

Reviewed: 2026-08-10

Answer: Publishing needs granted Meta scopes and a healthy connected token. If reconnect is required, reconnect Facebook/Instagram in Postifys and retry. See Security.

What this means in a real publishing workflow

Meta access depends on the permissions granted during OAuth and the assets managed by that Facebook identity. A token can be valid while the requested Page or Instagram account is no longer available to that user.

Recommended implementation

  1. Reconnect the correct Facebook identity through Postifys.
  2. Confirm the required Page and Instagram assets appear after refresh.
  3. Avoid storing Meta tokens inside n8n.
  4. Retry failed publishing only after the destination and permissions are confirmed.

How to verify the fix

Removing an admin role, changing a Page assignment, revoking the app, or changing a password can affect access. Reconnection is the safest recovery when refresh no longer restores the expected assets.

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

Technical reviewer: Postifys engineering (docs sourced from live API behavior). Contact support@postifys.com.

Continue learning

Token refresh versus reconnect

Postifys refreshes supported Meta tokens automatically when possible. A password change, revoked app access, expired refresh token, or permission downgrade still requires the account owner to reconnect from Postifys settings and confirm the Page or Instagram account appears in the connection list again.