The problem
A newsletter service, an internal tool or a platform without an official API falls outside every scheduler. You end up with a second calendar and a cron job nobody remembers.
How it runs
- 1Add a channel: Your own automation. Subscribe a webhook to post.publish_requested.
- 2At the post’s time staqly records the request with the text, the media and how long it will wait.
- 3Your receiver (n8n, a script) publishes wherever it should and reports the URL back.
- 4The target shows Published with your link, or Failed with your error and a Retry.
- 5Nothing reported within the collection’s limit fails the target, so nothing hangs forever.
Result
Every channel on one calendar, including the ones only your code can reach.
# staqly → you (signed webhook)POST /hooks/staqly X-Staqly-Event: post.publish_requested{"data":{"post":{"id":"post_oali...","content":"..."}, "channel":{"id":"ch_mine..."},"target":{"content":"..."},"timeout_seconds":3600}}# you → staqly$ curl -X POST $API/v1/posts/post_oali.../targets/ch_mine.../result \ -H 'Content-Type: application/json' \ -d '{"status":"published","url":"https://example.com/p/1790"}'Read the full recipe