Skip to content

Connect your CMS

Lyntcast reads and writes through each CMS’s own API. When you add a site it checks for write access, then re-tests every connection hourly and alerts you if it breaks, explaining the fix in plain words.

Add a site from Sites in your workspace. Credentials are encrypted before they are stored and are never shown to agents. Every site also gets a webhook URL so Lyntcast can notice edits made outside it.

WordPress (and WooCommerce)

  1. In Lyntcast, open Sites → Connect WordPress and enter your site address.
  2. You are sent to your own site’s Authorize Application screen (/wp-admin/authorize-application.php). Sign in if asked and approve the application named “Lyntcast”.
  3. Back in Lyntcast, the connection is saved. Lyntcast immediately replaces the Application Password that passed through your browser with a fresh one and deletes the original.
  4. Optional but recommended: install the Lyntcast plugin. If it is installed, it is configured automatically.
Field in LyntcastWhat to enter
Site URLYour site’s address, e.g. https://example.com
UsernameManual setup only: the WordPress user the Application Password belongs to
Application passwordManual setup only: Users → Profile → Application Passwords, create one named “Lyntcast”

Deleting through Lyntcast: Move to Trash (restorable).

Manual setup: use an account with the Editor role for posts and pages. For WooCommerce products, the account must also be able to manage products (Shop manager or Administrator).

WooCommerce products appear as the content type wc-products, using the same connection: prices, sale prices and dates, descriptions, SKU and stock.

Application Passwords need HTTPS (or a local development site).

Webhook: The plugin reports every change automatically. Without it, any webhook plugin can send post updates to the site’s webhook URL.

Shopifybeta

  1. In Shopify admin, open Settings → Apps and sales channels → Develop apps and create an app named “Lyntcast”.
  2. Under Admin API scopes, grant read_products and write_products.
  3. Install the app and copy the Admin API access token (it starts with shpat_ and is shown once).
Field in LyntcastWhat to enter
Store addressyour-store.myshopify.com (the .myshopify.com address, not a custom domain)
Admin API access tokenshpat_…

Deleting through Lyntcast: Archive the product (undoable).

Products, variant prices and compare-at prices are supported. Variant fields are addressed as variants.v<id>.price. Lyntcast uses the Admin GraphQL API (version 2026-10 by default).

Tested against a simulated API; not yet against a live store.

Webhook: Shopify admin → Settings → Notifications → Webhooks → Create webhook: “Product update”, format JSON, paste the site’s webhook URL.

Sanity

  1. Open sanity.io/manage, choose your project, then API → Tokens → Add API token.
  2. Name it “Lyntcast” and give it Editor permissions.
  3. Copy the token, and note the Project ID shown at the top of the project page.
Field in LyntcastWhat to enter
Project IDLetters, digits and dashes, e.g. abc123de
DatasetOptional, default production
API tokenThe Editor token

Deleting through Lyntcast: Delete, with a snapshot so undo restores the document.

Changes publish by default or can be saved as a draft. Portable Text is diffed word by word.

Webhook: sanity.io/manage → API → Webhooks → create, trigger on create, update and delete, paste the site’s webhook URL.

Contentful

  1. In Contentful, open Settings → CMA tokens and generate a personal access token named “Lyntcast”.
  2. Copy the token (it starts with CFPAT-). The account it belongs to must be able to edit and publish entries in the space.
  3. Find the Space ID under Settings → General settings.
Field in LyntcastWhat to enter
Space IDFrom General settings
EnvironmentOptional, default master
Content Management tokenCFPAT-…
LocaleOptional, default en-US. The locale agents read and write; other locales are left untouched
API hostOptional, default api.contentful.com. Use api.eu.contentful.com for EU data residency

Deleting through Lyntcast: Unpublish and delete, with a snapshot; undo recreates the entry with the same ID.

Webhook: Settings → Webhooks → Add webhook, select Entry events, paste the site’s webhook URL.

Ghost

  1. In Ghost admin, open Settings → Integrations → Add custom integration and name it “Lyntcast”.
  2. Copy the Admin API key (not the Content API key). It looks like 64f…:a1b…: a 24-character ID, a colon and a 64-character secret.
Field in LyntcastWhat to enter
Site URLe.g. https://blog.example.com (without /ghost)
Admin API keyid:secret

Deleting through Lyntcast: Unpublish (undoable).

Posts and pages are supported: title, HTML, excerpt, slug, feature image, featured flag, meta and Open Graph fields, and tags.

Webhook: Settings → Integrations → your Lyntcast integration → Add webhook: event “Post updated” (and “Page updated”), paste the site’s webhook URL.

Strapi 5

  1. In Strapi admin, open Settings → API Tokens → Create new API Token.
  2. Name “Lyntcast”, token type Full access, duration Unlimited. Save and copy the token.
Field in LyntcastWhat to enter
Strapi URLe.g. https://cms.example.com (without /api or /admin)
API tokenThe Full access token

Deleting through Lyntcast: Permanent in Strapi, so deletes always need approval; undo recreates the entry from the snapshot.

A change can publish or be saved as a draft; saving a draft leaves the live version untouched.

Webhook: Settings → Webhooks → Create new webhook: paste the site’s webhook URL and tick Entry: create, update, delete, publish, unpublish.

Webflowbeta

  1. In Webflow, open Site settings → Apps & integrations → API access → Generate API token.
  2. Grant CMS: read and write and Sites: read. Copy the token.
  3. Copy the Site ID from Site settings → General (24 characters).
Field in LyntcastWhat to enter
Site ID24 hexadecimal characters
Site API tokenThe generated token

Deleting through Lyntcast: Archive the item (undoable).

CMS collection items are supported. Tested against a simulated API.

Webhook: Site settings → Apps & integrations → Webhooks → Add webhook: trigger “Collection item changed”, paste the site’s webhook URL.

Catching edits made outside Lyntcast

Each site has its own webhook URL, shown under Sites → Catch edits that skip Lyntcast. It contains a secret token, so treat it like a password. When a CMS reports an edit Lyntcast didn’t make, the document’s history shows it, and pending changes that touch the same fields become conflicts instead of overwriting the newer content. See Webhooks & API.

Make Lyntcast the only way in

Lyntcast only governs changes that go through it. If someone gives an agent a CMS token directly, the agent can skip your rules. Give agents and automations Lyntcast access instead of CMS credentials, keep CMS tokens to the people who need them, and turn on webhooks so anything that slips past is reported.