Workflow guide
Track an automated post from acceptance to delivery
Keep Postly post IDs, distinguish scheduling acceptance from publication, and investigate failures without creating duplicate submissions.
Postly Team · Updated October 21, 2026
1.Keep the receipt
Store the post ID returned by Schedule Post or Schedule a Post. An accepted scheduling request is a reference to work in Postly, not a provider publication receipt.
2.Choose a status check
Use Zapier Find Post or Make Get a Post with that ID. Inspect the current post data and the scheduled item in Postly. Use the official API reference to interpret the fields returned by your endpoint.
3.Handle errors by cause
If authentication fails, inspect the connection and key. If the channel is unavailable, reconnect it in Postly. For content or schedule errors, correct the record before creating a new submission.
4.Avoid duplicate recovery
After a timeout, inspect the known post ID when available. If you must replay, retain the same source ID, text, channel, and date. Do not replace the date with the current time.
5.Keep checks proportionate
Use a sensible follow-up interval or your documented event workflow rather than aggressive polling. Review failures in Postly and keep the source record linked to its actual outcome.
Check the result
- The post ID survives across workflow steps.
- A failed row is not marked published.
- Provider errors are visible to the responsible teammate.
- Retries retain their original identity and schedule.