Connect your app to WordPress.com

Use WordPress.com as a headless CMS with Lovable: fetch posts, pages, and media for your app’s UI, and build workflows that publish or update content through a secure OAuth connection.

WordPress.com can work like a headless CMS: editors manage posts, pages, and media in WordPress, while your Lovable app fetches that content over the API and decides how it looks and behaves. The WordPress app + chat connector lets your app use WordPress.com’s APIs on your behalf after you sign in with a WordPress.com account.

WordPress.com is available as an app + chat connector: one shared connection that works in the chat while you build and in your published apps.

With WordPress connected, your app can:

• Load content from WordPress — list and read posts, pages, and related fields your account can access
• Build dynamic pages and layouts driven by CMS content instead of hard-coding copy in the repo
• Show blogs, marketing sections, and resource pages that stay up to date when editors publish in WordPress
• Combine WordPress content with the rest of your app — for example, sync or display selected posts alongside your own data
• Automate publishing workflows — for example, create or update drafts when you describe that behavior in chat (within what the API allows for your site)

The integration is built for WordPress.com, not for self-hosted WordPress. For self-hosted sites, see the WordPress integration.

Common use cases & example apps

Example app	Example prompt	Description
Marketing and landing pages	Use WordPress and build a marketing site where the homepage and key sections load titles, body, and images from my WordPress site.	Ship pages powered by CMS content. The app fetches posts or pages from WordPress and renders them as components so editors can update copy and media without changing app code.
Blog and editorial sites	Use WordPress and build a blog that lists recent posts and shows each post’s content, featured image, and excerpt.	Run a blog backed by WordPress. The app loads post lists and detail views from the API and reflects new publishes from the WordPress dashboard.
Resource or help center	Use WordPress and build a help center where each article is a WordPress page with search and categories.	Centralize articles in WordPress. The app queries pages or posts and builds navigation and article views from your CMS structure.
Product or listing-style content	Use WordPress and build a catalog-style page that shows items I maintain as posts (or custom content) with filters.	Present structured listings from WordPress. The app reads entries and fields exposed by the API and renders filters and cards based on your content model.
Event and announcement pages	Use WordPress and build a page that loads upcoming events from WordPress and sorts them by date.	Highlight time-based content. The app fetches posts or pages that represent events and orders them using dates you store in WordPress.
Editorial or publish workflows	When I submit this form, create a draft post on WordPress with the title and body I provide.	Turn submissions into drafts. The app creates or updates content through the API so editors finish work in WordPress.

Exact capabilities depend on what you ask Lovable to build, which sites your WordPress.com user can access, and the permissions you approve when connecting.

How WordPress connections work

• One connection is tied to the WordPress.com user who completes sign-in.
• That user’s visible sites and allowed actions follow WordPress.com’s rules and the scopes granted at authorization.
• You can create multiple connections (for example, separate accounts or environments) and link different projects to different connections where your workspace setup allows it.

When a project needs WordPress, Lovable may prompt you to allow or decline the integration for that project, depending on your preference.

How to connect WordPress.com

Workspace admins and owners can connect WordPress.com.

When a connection is created, WordPress.com becomes available across all projects in the workspace.

Prerequisites

• A WordPress.com account that can access the target site or sites
• Lovable workspace admin or owner role

Set up your WordPress connection

1. Open the WordPress connector

   Open Connectors and select WordPress.com.

2. Add a connection

   Click Add connection.

3. Name the connection

   In Display name, choose a clear name (for example, WordPress Marketing or WordPress Staging).

4. Connect to WordPress.com

   Click Connect (or the equivalent action). A WordPress.com authorization window opens. Sign in, choose the account if prompted, review the requested access, and approve. When you return to Lovable, the connection should show as active.

When connected, projects that are allowed to use this connection can call WordPress.com through Lovable’s gateway while you build and after you publish.

Use WordPress in a project

In chat, describe what you want using plain language and mention WordPress when it matters.

For example:

Use WordPress as the CMS. Load the five most recent posts from my site and show title, date, excerpt, and link on the homepage.

FAQs

Is this WordPress.com or WordPress.org?

The connector is built around WordPress.com. Self-hosted WordPress sites are a different product; they may still work with some WordPress.com or Jetpack flows depending on your setup, but you should assume this integration targets WordPress.com unless your site is explicitly connected in a way WordPress.com’s API supports.

Who pays for WordPress.com?

WordPress.com billing, plans, and any API-related limits are between you and WordPress.com. Lovable does not replace your WordPress.com subscription or quotas.

Who can create or delete the connection?

Workspace admins and owners add and remove WordPress connections. Other roles may still use the connector in projects when your workspace and project permissions allow it.

Are my WordPress tokens visible in my project?

No. With gateway-based connectors, credentials stay in the gateway. Your project does not store the OAuth tokens in plain view. See Gateway-based connectors.

Can each visitor to my app sign in with their own WordPress account?

The app + chat connector represents the connection you configured at the workspace level, not per-end-user WordPress login. If you need each user to authenticate to WordPress individually, you typically design a custom auth or API flow in your app rather than relying on this app + chat connector alone.

What if authorization fails or a site is missing?

Confirm you used the correct WordPress.com account, that the site appears in that account, and that you approved the requested permissions. If you changed passwords or revoked access at WordPress.com, reconnect the integration from Connectors using your connector’s reconnect or edit flow.

Limitations & troubleshooting

For underlying API concepts and endpoints, see WordPress.com developer documentation. Lovable exposes access through the connector; not every documented endpoint is used in every project.

• API coverage depends on WordPress.com, your site type, and permissions granted at connect time. Not every WordPress admin task is available through the API.
• Gateway limits apply per connector and project as described in Gateway-based connectors.
• If something works in the WordPress.com dashboard but not in your app, check whether the action is exposed to the API for your site and account.

Manage your connection

Connections are managed from Connectors: select , then open the connection.

• Unlink projects to remove access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
• Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use stop working until a new connection is added. See Delete a connection for the steps and who can delete.