Feed a schedule from a tiny service of yours

The problem

A daily tip, a weekly stat, a quote from your changelog: content that a function can produce, but that still needs a calendar, channels and a record of what went out.

How it runs

1. 1Create a schedule with "Call an endpoint that returns posts" and a secret.
2. 2Your endpoint verifies the signature and answers {"posts":[...]}.
3. 3The run creates the posts in the collection and publishes them to the schedule’s channels.
4. 4Drafts written by hand or by an agent are always picked first; the endpoint only fills the gaps.

Result

A stream that never runs dry, with every post on the calendar and in the history.