Skip to main content
WordPress.com hosts WordPress sites and blogs. The WordPress.com connector lets your Lovable app read and manage posts, pages, and media on the sites your WordPress.com account can access. Editors keep working in WordPress while your app decides how the content looks and behaves. It’s designed for headless CMS apps, blogs, marketing pages, and publishing workflows backed by a WordPress.com site. 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.com, your app can:
  • List and read posts, pages, and media from your sites
  • Create and update posts and drafts
  • Read site information
  • Manage categories and tags when you add the Taxonomy scope
  • Build pages and layouts from content that editors publish in WordPress
This connector is for sites hosted on WordPress.com. For a WordPress site you host yourself, use the WordPress (self-hosted) connector instead.

Common use cases and example apps

These examples show what you can build with WordPress.com, each with a prompt to start from.

How to connect WordPress.com

Who can create WordPress.com connections depends on your plan and workspace settings. App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans, they are effectively disabled at first: Who can create connections and clients defaults to No one until an admin changes it in Connectors → Admin settings → App + chat connectors. You can create multiple WordPress.com connections using different WordPress.com accounts or scopes, which is useful for separating environments or giving one project read-only access and another publishing rights. When the connection is created, you can link it to the projects where you want to use it. Anyone building in a project can ask Lovable in chat to link their project to it.

Prerequisites

Before connecting WordPress.com, make sure you have:
All API requests made through this connector run against your WordPress.com account. WordPress.com plans, limits, and billing are handled directly by WordPress.com, not Lovable.

Set up your WordPress.com connection

You authorize Lovable with your WordPress.com account. You do not need an API key or an application of your own.
1

Open WordPress.com in Connectors

Open Connectors and select WordPress.com. For the other places to open the catalog from, see Where to find connectors.
2

Add a connection

Click Add connection.
3

Name the connection

In Display name, name the connection (for example, WordPress.com Marketing). This name is only used inside Lovable to identify the connection.
4

Review scopes (optional)

Under Scopes, review the permissions the connection requests. Posts is always included, and Media, Sites, and User are selected by default.Select only the scopes your app needs. To add a scope later, edit the connection, select it under Scopes, and reconnect. For full scope documentation, see WordPress.com OAuth2 scopes.
5

Choose who can use this connection

Under Who can use this connection, decide who in your workspace can use the connection. You start as the only person with access:
  • Only you (default): leave the access list as is; only you can use the connection and its associated data.
  • Invite specific people: add workspace members by email; only you and the people you add can use the connection and its associated data.
  • Invite entire workspace: click Invite entire workspace to make the connection available to everyone in your Lovable workspace.
See Who can use connections and clients for more information.
6

Connect to WordPress.com and authorize

Click Connect. The WordPress.com authorization window opens, so make sure your browser doesn’t block pop-ups. If it does, Lovable redirects you instead.Sign in to WordPress.com if prompted, choose the account if asked, review the requested permissions, and authorize the app.You’ll be redirected back to Lovable with a confirmation.
When connected, anyone building in a project can ask Lovable in chat to link their project to WordPress.com (based on configured connection-level access). Your Lovable apps can then read and manage content on the sites your WordPress.com account can access. Requests go through Lovable’s connector gateway, so the WordPress.com tokens never enter your project. See WordPress.com documentation for more: WordPress.com REST API.

Working with more than one site

A connection is tied to the WordPress.com account you signed in with and reaches every site that account can access. When you prompt Lovable, name the site you want to work with, for example “load the five most recent posts from myblog.wordpress.com”. Lovable keeps the chosen site in your app’s backend code rather than asking visitors to pick one. If a site is missing, confirm you authorized with the WordPress.com account that owns it and approved the requested permissions.

Limitations

The WordPress.com connector cannot:
  • Perform actions the WordPress.com API does not expose for your site type and permissions. If something works in the WordPress.com dashboard but not in your app, check whether the action is available through the API for your site.
  • Receive WordPress.com webhooks or publish events.
  • Support per-end-user WordPress.com login. Each connection represents a single WordPress.com account shared across all projects linked to it.
If WordPress.com authorization is revoked from the WordPress.com side, reconnect the connection in Lovable before API calls can succeed again.

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.