WordPress (self-hosted)

Ownership and availability#

You own the WordPress installation, user, and Application Password. Obelo validates and encrypts the credential.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

CMS publishing requires an active Starter Pro plan or higher.

Before you connect#

• HTTPS is strongly recommended and /wp-json/wp/v2 must be reachable
• The connecting WordPress user can create posts and upload media
• Application Passwords are enabled on the site

Connect an existing account#

1. Open the provider in Settings → Integrations for the intended website.
2. Open the WordPress user's Profile page and create an Application Password for Obelo
3. Copy the site URL, username, and one-time password into the encrypted Obelo form
4. Let Obelo validate the REST API and publishing permissions

If you need a new resource#

1. Install WordPress with HTTPS on your domain or hosting provider
2. Create a dedicated Obelo publishing user with only the access it needs
3. Enable pretty permalinks and verify /wp-json/wp/v2 responds

Permissions to check#

• Use a dedicated WordPress user so access can be revoked independently
• Application Passwords are not your normal WordPress login password

Verify and troubleshoot#

Return with the site URL, username, and newly generated Application Password.

The site did not expose publishable post types. Check the REST API, user role, plugins, and permalink settings, then validate again.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access#

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.