Documentation / Publishing
How do I connect and publish to WordPress?
WordPress is a live publish adapter: TofuBofu writes finished articles as drafts you approve, then publishes them into your own CMS. This page covers connecting it, how we verify the connection, and what to do if it does not work the first time. For the full picture of every publish destination, see Integrations.
Connect
In WordPress, go to Users → Profile → Application Passwords, enter a name, and click Add. Copy the generated password and paste it below. Use an Admin or Editor account. Works on self-hosted WordPress and GoDaddy Managed WordPress.
| Field | What to enter |
|---|---|
| Site URL | e.g. https://yourfirm.com |
| WordPress username | the admin/editor user you created the app password for |
| Application password | wp-admin -> Users -> Profile -> Application Passwords |
Verify
The moment you save the connection, TofuBofu calls your site's own REST API as that user (/wp-json/wp/v2/users/me) and checks the account can actually publish, not just sign in. A green connection means that call succeeded against your live site just now, not that the password is merely the right shape.
Troubleshoot
It says "Authentication failed".
Check the username and application password. Application passwords are generated at Users → Profile → Application Passwords in wp-admin, and are separate from your login password. Use an Admin or Editor account.
It says "That user can sign in but cannot create posts".
The account generating the application password needs publish_posts or edit_posts capability. Use an Editor or Admin account, not a Subscriber or Contributor.
It says "The WordPress REST API was not found at that URL".
Confirm the site is actually WordPress and the URL is correct. Some hosts or security plugins disable the REST API entirely, which reads the same way.
Categories, tags or the author I expect are not offered.
Only terms and users your own site returns are shown. WordPress restricts the users list to administrators on many sites, so a hidden user list is normal and the site still connects; the author role is simply left unmapped.