Answer: Use Post History as the source of truth for multi-platform jobs. Meta inbound webhooks exist for specific cases; do not assume universal completion webhooks for every network yet.
What works today
- Post History / dashboard - primary status across lanes.
- API health -
/healthfor service readiness. - Meta inbound webhooks - configured for supported Meta events; not a full substitute for every platform’s final “live” state.
- n8n polling - Wait + HTTP Request / history lookup when you need workflow branching.
Honest limit: TikTok inbox uploads can succeed in Postifys while the creator still must finish publishing in TikTok. Status “accepted” ≠ always “public.”
n8n pattern
- Publish via Postifys node.
- Store returned identifiers.
- Wait / poll history until terminal success/fail or timeout.
- Branch notifications on outcome.
Related: webhooks overview · webhook docs · async publishing