Retrying only when it makes sense
A transient failure — network, 5xx, a rate limit — goes back in the queue. A permanent one, like refused credentials, is reported in the panel immediately instead of being retried five times for nothing.
Where it publishes
A client sets up a destination once. After that every published text goes there on its own, at the scheduled time.
Publishing through the official REST API with an application password. No plugin.
How it works → WWrites into a CMS collection through Data API v2, as draft or live.
How it works → GAdmin API with signed tokens, images into the Ghost library, tags.
How it works → GMarkdown into a static site repo — Astro, Hugo, Next and friends.
How it works → {}Signed JSON to your endpoint, or pull the content yourself through the API.
How it works → +Your system is not on the list and you have nobody to write the code? We build the integration; you change nothing.
How it works →The same for every destination
A transient failure — network, 5xx, a rate limit — goes back in the queue. A permanent one, like refused credentials, is reported in the panel immediately instead of being retried five times for nothing.
When you correct a published text, every destination receives the new version of the same post. Matching is done on an identifier, not on the URL, so a changed slug breaks nothing.
Application passwords, API tokens and webhook secrets are encrypted and used only for publishing. Deleting the integration deletes the secret.
WordPress, Webflow and Ghost have a connection check that says right away whether the credentials work — so it is not discovered on publishing day.
FAQ
Yes. One site may have several destinations — for example WordPress and a webhook to an internal system. Each keeps its own state, so a failure on one does not block the other.
That is what the webhook and the public API are for: we post signed JSON to your endpoint, or you pull the texts with a key. If you have nobody to wire that up, we build the integration ourselves — see Custom integration.
You choose per destination. Draft means the text waits for you inside your CMS; published means it goes out at the scheduled time.
The new version goes to every destination on its own and updates the existing post instead of creating a duplicate. The article URL does not change.
Next step
Connect any site — services, webshop or blog. The plan builds itself, articles are written and published on schedule, and the first one is free.