Skip to content
staqlyGet started

Know the moment a post went out, or failed

A scheduler you have to watch is a chore. Alerts bring the three things that matter to your phone: published, failed, reconnect needed.

The problem

A token expires quietly, a platform refuses a post at 9:00, and you learn about it from a reader at noon.

How it runs

  1. 1Create an alert: a Telegram, Slack or Discord bot, an ntfy topic or an SMTP account.
  2. 2By default it tells about post.published, post.failed and channel.needs_reconnect.
  3. 3Add schedule.posts_requested to hear when a collection runs dry, or post.scheduled for every new entry on the calendar.
  4. 4Each message links to the post in the dashboard; batch them with a digest window when a schedule publishes a lot.

Result

You find out before your readers do, and fix it from your phone.

Terminal
$ curl -X POST $API/v1/alerts -H 'Content-Type: application/json' -d '{    "name":"My phone","type":"ntfy",    "config":{"topic":"staqly-7f3k9q2","server_url":"https://ntfy.sh"},    "events":["post.published","post.failed","channel.needs_reconnect","schedule.posts_requested"]}'$ curl -X POST $API/v1/alerts/$ALERT_ID/test→ {"ok":true}

Read the full recipe

Plan the week once. Post every day.

Create a workspace in a minute, connect your channels and your agent, and let the schedule keep the rhythm.