Integrations

Publish where your site already lives.

63 platforms researched against their official APIs, and every card below says exactly where each one stands. 10 publish end to end today, connect, write, confirm what landed. The rest are labelled honestly: building, reachable through our webhook, or not connectable yet. Finding that out after you subscribe is not a discovery anyone should have to make.

Build my Growth Map

01 · Publishing destinations

Drafts in, published pages out.

Live connectors write through the platform's own documented API and keep its native states, no browser automation, no scraping. Where a platform has no draft state we refuse draft mode rather than quietly publishing. Everything not yet publishing says so on its own card.

The WordPress guide

A surveyed patch panel: a rail of publishing destinations on the left, sources on the right, cords arcing between them. WordPress sits at the top of the destination rail.

The connection field

WordPress first

The most common CMS leads the rack.

Most sites we crawl run WordPress, so its connector is the one the field notes cover in the most depth. Every other destination gets the same treatment: method, states, the honest note, and the fallback.

CMS & site builders

WordPress

Publish drafts or live posts with media, metadata, tags, and custom post types.

Connection: Application Password + REST API
States: Draft, scheduled, and live

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the WordPress guide

Ecommerce

Shopify

Build product-connected articles, buyer guides, and merchandising support pages.

Connection: GraphQL Admin API (articleCreate)
States: Draft, scheduled, and published

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the Shopify guide

CMS & site builders

Wix

Push structured drafts to Wix Blog and keep publication under customer control.

Connection: Wix app permissions + Draft Posts API
States: Draft and published

The honest noteContent is converted to Wix’s Ricos rich-content format before sending.

View the Wix guide

CMS & site builders

Squarespace

Editor-ready drafts formatted for paste-in publishing, because no blog API exists.

Connection: Guided export + import workflow
States: Editor-ready drafts

The honest noteSquarespace has no public blog API. We say so, and ship the honest workaround.

View the Squarespace guide

CMS & site builders

Webflow

Map your CMS fields once, then preserve staged and live publishing states.

Connection: OAuth + CMS Data API v2
States: Staged and live, per-item publish

The honest noteNo native scheduling in the API, so we time the publish call for you.

View the Webflow guide

Marketing suites

HubSpot

Create, update, and publish posts inside the marketing stack your team already uses.

Connection: OAuth + CMS Blog API v3
States: Draft, scheduled, and published

The honest noteBlog API access requires a Hub tier that includes the blog tool.

View the HubSpot guide

Developer & docs

Notion

Write structured pages and database items into the workspace your site reads from.

Connection: Notion API (OAuth integration)
States: Pages and database items

The honest noteContent appears publicly only on a published Notion Site or connected front end.

View the Notion guide

CMS & site builders

Ghost

Send clean editorial content through Ghost’s Admin API with preflight plan checks.

Connection: Admin API + short-lived JWT
States: Draft, scheduled, and published

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the Ghost guide

CMS & site builders

Framer

Synchronize content to editable collections without flattening the site’s design system.

Connection: Server API + managed collections
States: Synced and published

The honest noteThe Server API is new (2025) and publishing applies site-wide.

View the Framer guide

Ecommerce

BigCommerce

Publish store blog posts with SEO fields, tags, and settable publish dates.

Connection: X-Auth-Token (store content scope)
States: Draft and published

The honest noteThe blog rides BigCommerce’s legacy V2 API, which we monitor for deprecation.

View the BigCommerce guide

Ecommerce

Adobe Commerce

Create and update CMS pages and blocks for guides, landing pages, and support content.

Connection: REST + integration token
States: Active and inactive pages

The honest noteAdobe Commerce has no native blog, so we target CMS pages and blocks honestly.

View the Adobe Commerce guide

CMS & site builders

Drupal

Create nodes through JSON:API with publish state and scheduling support.

Connection: JSON:API + OAuth or Basic Auth
States: Published and unpublished, Scheduler-ready

The honest noteYour site must enable JSON:API write operations, which are off by default.

View the Drupal guide

CMS & site builders

Joomla

Create articles through the core Web Services API with scheduling support.

Connection: Joomla API token
States: Published, unpublished, and scheduled

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the Joomla guide

Headless CMS

Contentful

Create versioned entries with rich-text conversion and scheduled publish actions.

Connection: Content Management API token
States: Draft, published, and scheduled actions

The honest noteEvery update is version-checked against Contentful’s optimistic locking.

View the Contentful guide

Headless CMS

Sanity

Write Portable Text documents into your dataset, mapped to your studio schema.

Connection: Robot token + Mutations API
States: Draft and published

The honest noteFields map to your custom schema during setup, not a fixed template.

View the Sanity guide

Headless CMS

Strapi

Post entries to your collections with draft-and-publish state verification.

Connection: API token + REST
States: Draft and published

The honest noteWe read back every entry’s state after writing, because upstream draft bugs exist.

View the Strapi guide

Headless CMS

Storyblok

Create stories with structured content blocks, draft by default, publish on approval.

Connection: Management API token
States: Draft and published

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the Storyblok guide

Headless CMS

Prismic

Stage complete drafts into a Migration Release, ready for your one-click publish.

Connection: Migration API token
States: Drafts into a Migration Release

The honest notePrismic requires a human click to publish, by their design. We prepare everything else.

View the Prismic guide

CMS & site builders

Craft CMS

Save entries through GraphQL mutations with post dates and section mapping.

Connection: GraphQL mutations + schema token
States: Enabled, disabled, and post-dated

The honest noteRequires Craft Pro, and mutation scopes enabled on your schema.

View the Craft CMS guide

CMS & site builders

Umbraco

Create documents through the Management API with drafts and scheduled publishing.

Connection: Management API (OAuth client credentials)
States: Draft, published, and scheduled

The honest noteUmbraco 14 or newer; payload shapes vary with your document types.

View the Umbraco guide

CMS & site builders

Duda

Import blog posts into client sites as drafts with separate publish control.

Connection: Partner API credentials
States: Draft and published

The honest noteRequires a Duda agency or API plan; built for exactly this workflow.

View the Duda guide

Headless CMS

Payload

Post to your collections with draft status and your access-control rules intact.

Connection: API key + REST
States: Draft and published (_status)

The honest noteDrafts require versions enabled on the target collection.

View the Payload guide

Headless CMS

Directus

Create items in your collections, honoring the status field your schema defines.

Connection: Static token + Items API
States: Status field per your schema

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the Directus guide

Communities

Hashnode

Publish or draft posts to your Hashnode blog with canonical URLs preserved.

Connection: Personal access token + GraphQL
States: Draft and published

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the Hashnode guide

Communities

DEV (dev.to)

Cross-post articles with canonical URLs pointing back to your own domain.

Connection: API key (Forem API)
States: Draft and published

The honest notePositioned as cross-posting with canonical URLs; community rules apply.

View the DEV (dev.to) guide

Developer & docs

Git / MDX

Open commit-ready MDX or Markdown changes for review in your existing deploy workflow.

Connection: GitHub App or repository token
States: Branch, review, and merge

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the Git / MDX guide

Custom

Custom API

Receive finished, structured content at your endpoint under our webhook contract.

Connection: Your endpoint, our webhook contract
States: Whatever your workflow defines

The honest noteNo additional platform caveat beyond the connection method and publishing states shown above.

View the Custom API guide

Connect and publish with a provider-specific confirmation contract.

Connect it today and we read your own data from it.

Verify your site and send accepted URL-change notifications.

Credentials accepted and validated. Publishing is next.

Specified and scheduled, not connectable yet.

Reachable through our webhook if you run the receiving end.

On the roadmap. Nothing to connect right now.

02 · One workspace, every destination

One workspace, every destination.

Approved work leaves the Growth Map and lands where your site lives, under the review rules you set. We report what the destination confirms it stored, not what we sent it, and a re-run updates the page it already made rather than making a second one.

10publishing end to end today
27publishing destinations researched
36sources on the roadmap

Build my Growth Map Read the setup docs

Credential checks that name what is wrong before you save OnHTTPS enforced on every credentialed connection OnCapability checked at connect time, not on publish day OnDraft mode refused where the platform has none, never downgraded OnWe confirm what was stored, not what we sent OnRe-publishing updates in place instead of duplicating OnRetry history with clear exception ownership Planned

03 · Reads from & reports to

The layer around the publishing loop.

These are sources we read from rather than destinations we publish to, which is why the webhook is no substitute for them: it delivers outward, and these are inbound. Each one needs an OAuth connection we have not built yet, so none of them is connectable today. They are documented here because the plan is real and the scopes are decided, not because they are ready.