Getting started / Connect your CMS

Connect your CMS

The assistant reads and writes your content through your CMS's official API — there's no migration and no copy of your content on our side. Ten platforms are supported; each takes a couple of minutes to connect.

How connections work

  • Tested live before saving. When you paste credentials, we make a real API call to your platform and only accept the connection if it works — you'll see the result immediately.
  • Stored encrypted. Tokens are entered in masked fields, encrypted with AES-256 at rest, and never appear in any chat or transcript.
  • Least privilege. Scope tokens to just what's needed — one project, one site, the listed permissions. The instructions below name the minimal scopes.
  • Version requirements. Hosted platforms (Sanity, Contentful, Webflow, Shopify, BigCommerce) have no version to worry about — we track their current APIs. Self-hosted and plugin-based platforms have minimum versions, listed in each section below.

Sanity

Find everything at sanity.io/manage → your project. You need the Project ID, the dataset (usually production), and an API token: API → Tokens → Add API token with Editor permission.

Sanity supports a separate staging dataset — connect one and your team can rehearse content changes away from the live site. See Environments. Published changes go live immediately.

Contentful

In Contentful under Settings: the Space ID, the environment (usually master), and a Content Management (CMA) personal access token — Settings → API keys → Content management tokens (starts CFPAT-).

A staging environment can be connected alongside master. Publishing triggers your site's rebuild, so published changes are live in roughly 1–2 minutes rather than instantly.

Webflow

Site settings → Apps & integrations → API access → generate a Site API token with CMS read/write scopes. The Site ID is shown on the same page (optional — we detect it if omitted).

Item changes are staged by Webflow and published through the normal publish step, so nothing jumps onto the live site unexpectedly.

WordPress

Use an Application Password — WP admin → Users → Profile → Application Passwords — not your normal login password. The user needs the Editor or Administrator role. You'll enter the site URL, the username and that application password.

Requires WordPress 5.6 or later, served over HTTPS. Application Passwords shipped in core in 5.6 and WordPress disables them on non-HTTPS sites. The REST API must be reachable (it is by default — some security plugins turn it off). Custom post types appear automatically as long as they're registered with show_in_rest: true.

Drupal (headless)

Requires Drupal's JSON:API module (part of core since 8.7). If your API requires authentication, add a Basic-Auth username and password; if it's open enough for the needed operations, credentials are optional.

Requires Drupal 8.7 or later with the core JSON:API module enabled — any currently supported Drupal 10 or 11 site qualifies out of the box.

Shopify / Shopify Plus

In Shopify admin: Settings → Apps and sales channels → Develop apps → Create an app. Grant the Admin API scopes read_products, write_products (plus write_content for pages and blog articles), install the app, then copy the Admin API access token (starts shpat_). You'll also enter your yourstore.myshopify.com domain.

The assistant manages products, pages and blog articles.

WooCommerce

In WP admin: WooCommerce → Settings → Advanced → REST API → Add key with Read/Write — that covers products (keys start ck_/cs_). Optionally also add a WordPress Application Password (Users → Profile) so the assistant can manage posts, pages and images too.

Requires WooCommerce 3.5 or later (REST API v3) on a site served over HTTPS — WooCommerce only accepts API-key authentication over SSL. Managing posts and pages alongside products additionally needs WordPress 5.6+ (see the WordPress requirements above).

BigCommerce

Settings → Store-level API accounts → Create API account with the Products: modify and Content: modify scopes. The store hash is the code in your admin URL: store-XXXX.mybigcommerce.com.

Adobe Commerce (Magento)

In the admin: System → Extensions → Integrations → Add New Integration with the Catalog and Content resources, then Activate it and copy the Access Token. You'll enter your store URL and that token.

Requires Magento 2 — Adobe Commerce or Magento Open Source 2.x (we test against 2.4, the currently supported line). Magento 1 is not supported.

Optimizely CMS (SaaS)

For the fully hosted Optimizely CMS (SaaS): in your CMS go to Settings → API Keys → Create API Key and copy the client ID and secret (grant the key content edit and publish rights under Settings → Set Access Rights). Optionally add your site's root container key — the content item your pages live under — as the default home for new content.

Optimizely's content is natively versioned: the assistant's drafts are draft versions, publishing promotes them live, and your CMS approval workflows are respected. Running classic Optimizely / Episerver (CMS 11/12 in DXP)? That connects through our Enterprise guided setup — its Management API is installed per site by your developers. Contact us.
On platforms where a published item has no separate draft version (WordPress, Drupal and the commerce platforms), editing live items requires publish permission — users without it create new drafts instead and route changes through approvals. This protects live and revenue-bearing content.
← Quickstart Connect your repository →