Skip to content
staqlyGet started

Publish through n8n or your own script, keep the calendar

Staqly cannot reach every platform, and some publishing steps are yours alone. Add a channel that hands the post to your code; the post’s status and history look like any other.

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

  1. 1Add a channel: Your own automation. Subscribe a webhook to post.publish_requested.
  2. 2At the post’s time staqly records the request with the text, the media and how long it will wait.
  3. 3Your receiver (n8n, a script) publishes wherever it should and reports the URL back.
  4. 4The target shows Published with your link, or Failed with your error and a Retry.
  5. 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.

Your receiver
# 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"}'

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.