Workflow guide
Turn an approved content calendar into scheduled social posts
Design an approval-driven Zapier or Make workflow with explicit channel selection, timezone-aware scheduling, and retry recovery.
Postly Team · Updated October 21, 2026
1.Define the publishing record
Keep the final text, publishing date with timezone, workspace, channel, source record ID, approval state, and returned Postly post ID as separate fields.
2.Use an approval event
Start the automation only when the content becomes ready for publishing. Filter out records that are incomplete, unapproved, or already linked to a Postly post.
3.Route to a connected destination
Use the Postly connector to choose the workspace and channel. In Make, discover the channel ID and platform identifier before mapping the scheduling module.
4.Schedule once and keep the ID
Submit a future publishing time and the stable source record ID. Write the returned Postly post ID back to the record. Keep retries unchanged so an uncertain outcome can recover the same submission.
5.Review changes separately
A changed caption or date is a new submission to this connector. Check the existing scheduled item before resubmitting edited content. Manage changes in Postly or through the documented post-management API.
Check the result
- Only approved records reach the action.
- A source record does not keep retriggering after write-back.
- A timezone is explicit.
- Every accepted request is linked to a Postly post ID.