Integration

Custom integration

The webhook and the public API cover any system that can receive or make an HTTP call — but somebody on your side has to wire it up. If you have nobody, that part is ours: we look at how your site accepts content and build the connection end to end.

What we need from you

  • The site address and a short note on what it runs on (if you know — if not, we work it out).
  • A contact who can approve access: the site administrator, the host, or your developer.
  • One way for us to write a post: an API, database access through a service account, FTP/Git deploy, or an account in your CMS.
  • A staging environment if you have one. If you do not, the first posts go out as drafts on production.

What lands on the destination

  • The same payload as any ready-made integration: title, body with H2/H3 structure, lists and an FAQ block
  • SEO title, meta description and slug
  • A featured image with alt text — moved onto your side where your system allows it
  • Category and keywords, mapped onto the structure you already have
  • The scheduled publish time, and later edits that update the same post

How it works

The publishing flow, step by step

01

1. A call and a look at the system

A short call and a review of the site: what it runs on, how articles are entered today, who has access, and where the text has to land. That tells us whether a working API already exists or the path has to be built from scratch.

02

2. A proposed publishing path, before any code

You get it in writing: how the text gets in, which fields we fill (title, body, slug, meta description, image, category), what stays on your side, and how long the build takes. If no path exists, it also says what would have to be added on your end.

03

3. Build and test on drafts

We build the integration and run it in draft mode first. A few test articles travel the whole way to your site, and you see them before anything becomes public.

04

4. A field-by-field check

We walk one post through together: is the title in the right place, are the images in your media library, does the meta description reach the field your SEO plugin actually reads, does the category match your structure.

05

5. Going live on the calendar

Once it lines up, we switch to scheduled publishing. From then on the integration behaves like any ready-made one — the same retries, the same error reporting, the same handling of edits.

06

6. Maintenance

If your site changes — a new CMS version, a changed schema, a different host — we adapt the integration. A failure shows up in the panel; it is not discovered a month later by the silence.

Limits

What this integration does not do

It's on the page on purpose. Better seen now than after the first publish.

  • We do not promise an integration before seeing the system. If no publishing path exists and none can be built without changes on your side, you hear that at the review — not after paying.
  • The build is billed once, separately from the subscription: $99 per integration (regularly $199). If the system requires substantial work, the price is in the proposal before work starts.
  • We do not take over maintaining your site. We maintain the connection to it; everything behind that stays yours.
  • Systems with no programmatic way in at all — hand-edited static HTML, closed portals with no access — stay out of reach. There the only path is publishing by hand from our panel.

FAQ

Common questions — Custom integration

How long does it take?

For a system with a usable API, usually a few working days. For a system where the publishing path has to be built first, the deadline is in the proposal — before work starts, not after.

What if I have my own developer?

Then the webhook or the public API is often faster: we post signed JSON, they receive it on your side. The documentation is public and we stay available until it works.

Do you need database access?

Not necessarily. We ask for the smallest access that works — an API key or a CMS account. Writing straight to the database is the last option and only used when there is no other way.

What happens if I cancel?

We stop publishing and delete the stored credentials. Everything published up to then stays on your site — it is your content and we do not pull it back.

Does this work for a site that is not in English?

Yes. The integration does not depend on the content language — planning and writing happen in your market's language, and publishing goes through the path we build.

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.

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.

Start free Talk to us first