Trigger: an article has been published
Every few minutes the tool asks our API what was published after the time of its last question. Only what is new comes back, with the title, the address and the body — without walking the whole archive.
Integration
Zapier
The Zapier app is not in their store yet — and that is written here so you do not find out when you go looking for it. Everything it will do already works through our public API; it just takes one step more.
This integration does not work yet — it is in preparation. Everything described below already exists in the public API, so Make and n8n do the same job today.
What we need from you
- An API key from the Inowara panel — one for reading, a separate one for writing.
- An account on Zapier, Make or n8n.
- Until the app is published: Webhooks by Zapier in Zapier, a plain HTTP component in Make and n8n.
What lands on the destination
- Title, address, slug and publish date of the article.
- The body as HTML, markdown and plain text.
- Keywords, category, SEO score and the featured image.
- The language of the article and its translation group, for sites in several languages.
How it works
The publishing flow, step by step
Action: add a topic
From any tool you can push a topic into our queue. It enters the same flow as a topic from the planner: written, checked, published on schedule.
Action: publish an article
An article waiting for approval can be published from outside — for example when your editor approves it in the tool they already use.
What the app itself changes
Nothing about what can be done. It changes how many steps it takes: instead of wiring an HTTP call and a key by hand, Inowara appears in the app list and connects in two clicks.
Limits
What this integration does not do
It's on the page on purpose. Better seen now than after the first publish.
- The app is not published in the Zapier store yet — their review takes weeks and does not depend on us.
- A write key spends quota or credits, like any other topic. That is why it is issued separately from a read key.
- The trigger is polling: the tool asks every few minutes. For an instant push there is the webhook, which already exists.
FAQ
Common questions — Zapier
Can I do anything today, without that app?
You can do all of it. Make and n8n work with a plain HTTP component, and Zapier with Webhooks by Zapier. When the app ships, the same flow moves onto it with no change on our side.
Why do you need Zapier at all if you have an API?
For the people who have nobody to hand an API to. Zapier connects Inowara to thousands of tools without a line of code — Notion, Slack, Google Sheets, an internal CRM.
When exactly does it arrive?
Our side is done. What remains is submitting the app and passing their review; that takes weeks and we do not control its speed. We do not promise a date before it passes.
Other integrations
One site can publish to several destinations at once
WordPress Publishing through the official REST API with an application password. No plugin. Webflow Writes into a CMS collection through Data API v2, as draft or live. Ghost Admin API with signed tokens, images into the Ghost library, tags. GitHub Markdown into a static site repo — Astro, Hugo, Next and friends. Webhook and public API Signed JSON to your endpoint, or pull the content yourself through the API. Custom integration Your system is not on the list and you have nobody to write the code? We build the integration; you change nothing.
Next step
Ready for organic growth?
Connect any site — services, webshop or blog. The plan builds itself, articles are written and published on schedule, and the first one is free.