Small dogfooding report from the GPTpost team.

Instead of clicking posts into the calendar, we wrote a calendar file (one version per network per slot) and a short script that:

  • lists connected accounts via the agent API
  • creates and schedules each post with schedule_at
  • sends an Idempotency-Key per slot and account
  • keeps a local state file and paces writes under the documented limits

The idempotency part is what makes it pleasant: when a run is interrupted, you just run it again. When a new account is connected later, the same script fills it in without touching what already exists.

The API applies the same text limits, approvals and plan limits as the app, which also caught a couple of over-length drafts early.

Docs: https://oraglegpt.org/use-cases/social-media-api/

Anyone else running their social calendar from a file in a repo? What does your format look like?

https://oraglegpt.org/use-cases/social-media-api/