Connect WordPress CMS to Devad POST
Connect WordPress posts or pages with optional subsite REST base, tags, categories, and SEO/meta fields.
What this channel does
- WordPress CMS uses a tenant site URL, optional REST base, username, and application password.
- Only superadmin-enabled and plan-allowed channels appear to tenants in POST.
Before you start
- A WordPress user that can create posts.
- A WordPress application password.
- HTTPS and a working WordPress REST API.
- For multisite, the exact subsite REST base URL when it differs from the site URL.
Connect in Devad POST
- Open `/workspaces/apps/post/channels` and choose WordPress CMS.
- Site URL: the public site or subsite URL.
- REST base URL: optional, for example `https://example.com/subsite/wp-json/wp/v2`.
- Username: WordPress username.
- Application password: generated in WordPress user profile.
- Save the connection and confirm the channel appears as connected.
Publish with this channel
- Choose post or page.
- Optionally set slug, excerpt, author ID, category IDs, tag IDs, and featured media ID.
- For SEO, choose None, Generic meta, or SiteSEO and fill title, meta description, focus keyword, canonical URL, and Open Graph fields.
Common fixes
- 401: recreate the application password and confirm username.
- 404: check the REST base URL, especially for multisite.
- Invalid meta: select None or confirm your SEO plugin registers REST meta fields.
Security notes
- Never paste tokens, webhooks, passwords, or API keys into tickets, screenshots, public docs, or AI prompts.
- Use a credential dedicated to Devad POST and revoke it if access changes.
- Use HTTPS endpoints only.