WordPress (self-hosted) Connector

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want WordPress (self-hosted) Connector working in a real project rather than a sandbox.

   Set up WordPress (self-hosted) Connector in this project — read and manage posts, pages, and media on self-hosted WordPress sites. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Content dashboards

   The record lists this as one of the jobs WordPress (self-hosted) Connector is meant for, so it is a fair first test of whether it fits your app.

   In this project, use WordPress (self-hosted) Connector for content dashboards. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   WordPress (self-hosted) Connector is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses WordPress (self-hosted) Connector before I publish. Check read posts and pages and publish and update content, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Editorial tooling

   A second job the record lists for WordPress (self-hosted) Connector, useful once the first path works.

   Extend this project so WordPress (self-hosted) Connector also covers editorial tooling. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is WordPress (self-hosted) Connector?

  WordPress (self-hosted) Connector is Lovable's App Connectors feature: Read and manage posts, pages, and media on self-hosted WordPress sites. WordPress (self-hosted) lets apps read and manage posts, pages, media, users, and custom post types on any self-hosted WordPress site through the REST API.

• Is WordPress (self-hosted) Connector GA or in beta?

  WordPress (self-hosted) Connector is generally available (GA) on Lovable.

• What Lovable plan includes WordPress (self-hosted) Connector?

  WordPress (self-hosted) Connector is available on all Lovable plans.

• When did WordPress (self-hosted) Connector launch?

  WordPress (self-hosted) Connector launched on Jul 2, 2026.

• Connectors page in projectsSame category, also GA · Jul 2026
• Bulk-edit your Shopify catalog in one approvalSame category, also GA · Jul 2026
• Connect KLIPY in one click, no API keySame category, also GA · Jul 2026