7.2 · Connect WordPress
When to connect your WordPress site to GrowthOS, how to create an application password, and the setup wizard from connection to first published draft.
GrowthOS can publish finished articles straight into your WordPress site: pick a post type, click publish, and the article lands as a WordPress draft with formatting intact, images in your media library, and the cover set as the featured image. The connection is a one-time setup of about five minutes. This guide covers when you need it, what to gather before you start, the setup wizard step by step, and what publishing looks like once it's live.
When to connect
Connect WordPress as soon as your workspace is producing articles that end up on your WordPress site. The signals that it's overdue:
- Someone is copy-pasting. Articles are finished in GrowthOS, then manually recreated in the block editor: headings rebuilt, images re-uploaded, the featured image and slug set by hand. Every article costs 15 to 30 minutes of pure transcription, and every transcription is a chance to drift from the reviewed version.
- Formatting keeps breaking in the move. Tables collapse, lists lose their structure, or pasted content drags along styling that fights your theme. The publishing pipeline ships clean article HTML that WordPress accepts as-is, so this whole class of problem disappears.
- Publishing volume is ramping. Moving from a couple of articles a month to a weekly cadence makes the copy-paste tax immediate. Connect before the ramp, not after.
If your site is not on WordPress, the same flow exists for Webflow, Sanity, and Strapi; only the credentials step differs. And with no connection at all, GrowthOS still supports manual publishing (mark the article published and paste the live URL), so nothing blocks while you wait on access.
What you'll need
- A WordPress user who can publish posts (Editor or Administrator role), and access to their profile to create an application password.
- Your site served over HTTPS. WordPress only offers application passwords on secure sites.
- A GrowthOS login that can manage publishing. If you don't see CMS Connections under Workspace Admin, ask your GrowthX team to enable it.
- Five minutes with both tabs open.
How to connect
Create an application password in WordPress
In your WordPress admin, go to Users → Profile for the user GrowthOS should publish as, scroll to Application Passwords, name one (something like "GrowthOS"), and create it. Copy the generated password immediately; WordPress shows it only once.
An application password is not the user's login password: it's a revocable key scoped to API access, and you can delete it from the same screen at any time without touching the account.
Published posts carry this user as the author, so pick the account you want on the byline (or a dedicated publishing user), not whoever happens to be setting up the connection.
Connect the CMS in GrowthOS
In GrowthOS, go to Workspace Admin → CMS Connections and click Connect a CMS. Pick WordPress from the cards and fill in the form:
- WordPress site URL: your site's address, for example
https://blog.example.com. - Username: the user the application password belongs to.
- Application password: the value from step 1.
Leave the live-publishing switch off for now; it's the right default, and you can flip it later from this same screen once you trust the pipeline (see how publishing works).
Submitting lands you on the connection's settings screen, and GrowthOS immediately reads your site's post types. Within a few moments the header fills in with how many it found: posts, pages, and any custom post types your site registers. If your site's structure changes later, Re-read refreshes the picture without disturbing anything already set up.
Add the blog post type
Click Add a post type and pick where your articles live (usually Posts). The dialog lists every publishable post type on your site and warns you if the one you picked has no content field, which usually means it's the wrong one. Confirming opens that post type's setup wizard.
Review and confirm the field mapping
GrowthOS proposes a mapping from its article fields (title, slug, body, meta title, meta description, cover image) to the post type's fields, with a reason for each suggestion. Custom fields your site exposes over the REST API, including ACF fields, are discovered and mappable too. Review it in the confirm form: required fields are listed first and marked, each field has a source picker, and anything GrowthOS shouldn't touch can be left unmapped or given a fixed value. The form blocks you if a required field is uncovered or the article body has no home, so you can't confirm a broken mapping.
Run the test article
The wizard stages a sample article on your site as a draft, then shows you exactly what WordPress received, field by field, with a link to open the real post. This is your proof the mapping works before any real content moves. Check that the body kept its structure (headings, lists, links, tables) and that every mapped field carries the right value.
Finish
The last step recaps the post type, the mapping, and the test round trip. Finishing marks the post type ready and deletes the sample draft from your site, so nothing is left behind. You can add more post types to the same connection later (pages, a resources post type); each gets its own mapping and its own wizard pass.
How publishing works after setup
Every article in GrowthOS now has a working Publish step. Pick the post type, publish, and watch the card update as the article lands.
- New articles arrive as drafts. Publishing creates the post with draft status; nothing appears on your live site until someone presses Publish in WordPress, or GrowthOS promotes it with the connection's live-publishing switch on (it starts off).
- Updates flow through the same button. Edit the article in GrowthOS and publish again; the existing post is updated in place. Republishing an unchanged article does nothing rather than creating a duplicate.
- Images live in your media library. Inline images upload to the media library and the body references them there; the cover image uploads too and is set as the post's featured image. The published page never loads assets from GrowthOS.
- Formatting survives. The article ships as clean structural HTML that holds up through WordPress's own content filtering, tables and code blocks included.
Known limitations
WordPress has no separate staging layer for a post that is already live. Updating an already-published post writes the live page immediately, even with live publishing off; the draft state only protects posts that have never been published. Once an article is live, treat a republish from GrowthOS as a live edit.
- SEO fields depend on what your site exposes. WordPress doesn't accept writes to fields the site never registered for API access, so meta title and description are mappable only when your SEO setup exposes them (most SEO plugins can). If they don't appear in the mapping, that's the reason; ask your GrowthX team about exposing them.
- Inline images re-upload on each publish. Republishing an edited article uploads its inline images to the media library again rather than reusing the earlier copies. Harmless for the published page, but a heavily-republished article accumulates copies in the library.
Troubleshooting
- The connect step rejects the credentials. Check the pair together: the username must be exactly the account the application password was created under, and the site URL must be the address your admin actually lives at (if your site redirects, use the final address). Application passwords also require HTTPS; on a plain-HTTP site WordPress disables them entirely.
- A post type you expected isn't listed. Only post types exposed through the REST API are discoverable. Standard posts and pages always are; a custom post type registered without REST support won't appear until your developer enables it.
- A publish is refused because the post type changed. Your site's fields changed (a plugin update, an ACF change), and GrowthOS pauses that post type rather than publish into a structure it no longer recognizes. Open the post type in CMS Connections and re-run the mapping against the refreshed schema; other post types on the connection keep publishing throughout.
Where to go next
Last updated at August 19, 2026
7.1 · Connect Webflow
When to connect your Webflow CMS to GrowthOS, how to generate the right API token, and the setup wizard from connection to first published draft.
7.3 · Connect Sanity
When to connect your Sanity project to GrowthOS, the API token and project details to gather, and the setup wizard from connection to first published draft.