Integrations declare what they can actually do
Every connector has a common contract: connection test, destination list, field mapping, media upload when supported, draft, publish, update, status read, public URL, disconnect and revoke. What the service does not allow is declared here.
| Service | API type | Authentication | Capabilities | Declared limits |
|---|---|---|---|---|
| WordPress (self-hosted) | REST API v2 + Application Password | Application Password (HTTPS) | Destinations, drafts, publish, update, media, categories, tags | Requires WordPress 5.6+ with REST API enabled and permalinks other than “plain”. The optional plugin adds publication verification and status. |
| Shopify | Admin GraphQL API | Custom app / access token | Blog, articles, drafts, publish, update, article images | The blog must exist. Required scopes depend on the API version; rate limits are Shopify’s. |
| Ghost | Content API + Admin API | Admin API key (id:secret) | Posts, drafts, publish, update, tags, cover images | A custom integration in the Ghost panel is required. The API version is indicated in the base URL. |
| Webflow | Data API v2 | Site token | CMS Collection: create and update items, publish items | Fields must exist in the Collection. Site publishing stays separate from item creation. |
| Wix | Wix Blog API | API key + site | Wix Blog drafts and posts, update | Requires a plan with Wix Blog and a custom app. Some operations vary by site type. |
| Framer | Plugin / Server API | Plugin installed on the project | Send content to the plugin, create a draft | Framer does not offer a generic public CMS API: our plugin is required and publication verification stays manual. |
| HubSpot | CMS Blog Posts API v3 | Private app token | Blog posts, drafts, publish, update, tags, author | The blog must exist in the portal. CMS scopes are required. |
| Own blog / BlogBowl | Dedicated connector | Service credentials | Drafts and publication according to the available APIs | Effective capabilities are detected at connection time and shown clearly. |
| Notion | Notion API | Internal integration token | Deliver content as pages in a database | This is an editorial delivery, not a web publication: it does not produce a public URL. |
| Generic webhook | Signed HTTP POST | HMAC-SHA256 on the body + timestamp | Event delivery, retry with backoff, delivery history, anti-replay, idempotency by event ID | The receiver must verify the signature and respond 2xx. It is not a CMS connector: publication is performed by your endpoint. |
| Zapier / n8n | Compatible webhook | Webhook URL + signature | Trigger external automations on product events | Compatibility via webhook: there are no published apps on the respective marketplaces. |
| Google Search Console | Search Console API + URL Inspection API | OAuth 2.0 with a verified property | Clicks, impressions, CTR, position by page/query/country/device; URL inspection within quota limits | Authorised properties only. Data arrives with a delay declared by Google. The Indexing API is NOT used for ordinary articles: it is reserved for JobPosting and BroadcastEvent. |
A generic webhook is not the same as a native connector: each connection status distinguishes configured, reachable, authenticated, delivery verified and publication verified. A homepage that returns 200 does not prove a publication.
Need an integration that is not listed?
Tell us which service you use: if it has a documented API it can enter the registry, with capabilities and limits written before it is even implemented.