Safe automation

Auto-publish that behaves like a promise.

Enabling auto-publish takes a deliberate confirmation naming exactly what will happen and when. After that, every publish rechecks connection health, balances, and content rules, and one button pauses everything.

  • Explicit consent
  • Pre-flight rechecks
  • Global pause

Consent first, always

Activation for an auto-publish Tempo shows the Organization, Channel, plain-language recurrence, timezone, next five times, estimated usage, and current limits, then requires an acknowledgement: publishing will happen at these times while active, pausable at any moment.

  • Valid drafts only, inside the configured window
  • Connection health revalidated immediately before publish
  • Moderation and prohibited-topic rules reapplied
  • Ambiguous provider timeouts reconciled before retrying

Brakes within reach

Pause a single Tempo, an entire Organization, or everything via emergency stop. Pausing stops new publish claims immediately without deleting drafts or future occurrences, and it lands in the audit log.

Idempotency makes retries boring

Stable operation keys mean a retry after a network blip updates a record instead of duplicating a post. Boring is the goal.

Straight answers

Questions, answered.

Is auto-publish the default?

No. New Tempos default to Review required. Switching to auto-publish is a deliberate act with its own confirmation screen.

What happens if the platform API is down at publish time?

Attempts fail safely with classified errors and bounded retries. Ambiguous outcomes reconcile against provider references before any retry, preventing duplicates.

Can I auto-publish and still spot-check?

Yes. Published history shows every attempt and outcome, and you can flip any Tempo back to Review required instantly.

Set the next beat

Ready to set your first Tempo?

Start free, describe your brand once, and watch the next ten post times appear before anything goes live.