Your own automation

Your own automation (provider custom) is a channel without a platform behind it. When a post targets it, staqly does not publish anything itself: it records what it wants published, tells your webhook receiver or agent, and waits for the result. Use it for a platform staqly does not reach yet, an internal tool, a newsletter service, or a dry run of the whole loop without any external account.

How it worksCopy Anchor Link

1. When the post is published (by hand, at its time, or by a schedule), the target on your channel becomes publishing and staqly records post.publish_requested with the post, the channel, the target's text and settings, and how long it will wait.
2. Your automation learns about it through a webhook subscribed to post.publish_requested, or by polling GET /v1/work (MCP list_requested_work), which lists every target that waits for a result.
3. It publishes the content wherever it should go, then reports the result with POST /v1/posts/{id}/targets/{channel}/result: published with the URL and the platform's id, or failed with an error.
4. The target takes that status; the post settles when its last target does. Nothing reported within the collection's processing timeout (processing_timeout_seconds, else the server's PROCESSING_TIMEOUT, default 1 hour) fails the target with No result reported.

Let staqly call your endpointCopy Anchor Link

Give the channel an Endpoint URL and staqly calls it itself for every post, instead of only emitting the event. Set it when you add the channel, or later with Edit connection in the channel's menu:

The JSON body:

{
  "post_id": "post_3wq8m2kd7hz5vn4yjx6a",
  "channel_id": "ch_7h2kq9xw3nbvd5yhzm6a",
  "text": "Release 0.9 is out.",
  "media": [{ "id": "med_...", "name": "cover.png", "mime_type": "image/png", "size": 48213, "url": "http://localhost:3333/v1/media/med_..." }],
  "tags": ["release"],
  "settings": {},
  "thread": [{ "content": "Details in the changelog.", "media": [], "delay_seconds": 300 }]
}

How staqly reads the reply:

thread lists the post's replies (text, media with URLs, the wait after the part before): your automation publishes them itself, so staqly marks them skipped on this channel. The post.publish_requested event carries them too, in target.thread.

The call goes through the same guard as webhooks: in cloud mode private and loopback addresses are refused. Every request carries User-Agent: staqly and X-Staqly-Post with the post id.

Set it upCopy Anchor Link

curl -s -H "Authorization: Bearer $STAQLY_API_KEY" -X POST http://localhost:3333/v1/channels -H 'Content-Type: application/json' \
  -d '{"provider":"custom","name":"My publisher"}'
# → {"id":"ch_7h2kq9xw3nbvd5yhzm6a","provider":"custom","status":"connected", ...}

curl -s -H "Authorization: Bearer $STAQLY_API_KEY" -X POST http://localhost:3333/v1/webhooks -H 'Content-Type: application/json' \
  -d '{"url":"https://n8n.example.com/webhook/staqly","events":["post.publish_requested"]}'

curl -s -H "Authorization: Bearer $STAQLY_API_KEY" http://localhost:3333/v1/work

{
  "data": [
    {
      "kind": "target",
      "requested_at": "2026-10-20T09:00:02Z",
      "post": { "id": "post_oalirbz67y4m4cqxq5dw", "content": "v1.4 is out.", "media_items": [], "targets": [ { "channel_id": "ch_7h2kq9xw3nbvd5yhzm6a", "status": "publishing" } ] },
      "channel": { "id": "ch_7h2kq9xw3nbvd5yhzm6a", "provider": "custom", "name": "My publisher" }
    }
  ]
}

curl -s -H "Authorization: Bearer $STAQLY_API_KEY" -X POST http://localhost:3333/v1/posts/post_oalirbz67y4m4cqxq5dw/targets/ch_7h2kq9xw3nbvd5yhzm6a/result \
  -H 'Content-Type: application/json' \
  -d '{"status":"published","url":"https://example.com/p/1790","external_id":"1790"}'

# or
  -d '{"status":"failed","error":"Instagram API quota exceeded"}'

What the person seesCopy Anchor Link

In the post, the target shows Publishing while your automation works, with how long it has waited of the limit, then Published with the link you reported or Failed with your error and a Retry button. A retry records a new post.publish_requested. The collection's settings have Fail publishing if nothing is reported within for the timeout; Default names the server's value.

Alerts subscribed to post.publish_requested say Your automation is asked to publish; the default alert events tell about the final post.published or post.failed.

TipsCopy Anchor Link

• Deduplicate on the event id. Webhook deliveries are at-least-once; the same request can arrive twice. Keep the last few X-Staqly-Event-Id values and skip repeats.
• Report only what you did. Reporting a target that another system published is how a post ends up twice on a platform.
• Use Idempotency-Key on the result request if your automation may retry it; the API replays the first answer for 24 hours.
• Timeouts are per collection. A newsletter that takes an hour to send gets a long limit; a chat bot that answers in seconds gets a short one.

Next stepsCopy Anchor Link