Answer: Documented webhooks are Meta inbound callbacks to Postifys. For your own systems, use publish responses, Post History, and polling. Details: Webhooks and Status.
What this means in a real publishing workflow
Status tracking should distinguish submission acceptance from final platform publication. Postifys records queue, processing, published, and failed outcomes in Post History, while provider-specific inbound webhooks are separate from outbound publishing completion.
Recommended implementation
- Save the submission ID returned by each platform call.
- Poll status on a backoff schedule suitable for large media uploads.
- Stop polling on published or failed.
- Send alerts containing the platform, destination, Postifys ID, stage, and actionable failure reason.
How to verify the fix
Do not invent a webhook guarantee that the integration does not expose. Where a final outbound webhook is unavailable, polling Post History is the honest and reliable control path.
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