Documentation
Nina writes your blog posts, sources the images, and publishes them into your own CMS. To do that we need one narrow, revocable credential from you. These guides show exactly how to create it, what it can and cannot reach, and how to take it back whenever you want.
Pick your CMS
Each guide is written for the person doing the clicking, with the exact menu labels, the exact permissions to grant, a way to check it worked before you send it, and a troubleshooting section for when it does not.
WordPress
A dedicated Editor user and an Application Password. No plugins, no code. Covers self-hosted, WordPress.com and Jetpack.
Read the guide → ReadyShopify
A Dev Dashboard app with four content and file scopes. Updated for Shopify’s January 2026 change that retired legacy custom apps.
Read the guide → ReadyWebflow
A site API token with CMS and Assets permissions. Works on Premium and above; Basic has no CMS to publish into.
Read the guide → ReadyHubSpot
A private app token with the content and files scopes. Includes the tier check worth running before you start.
Read the guide → ReadyWix
An account API key scoped to your one site. Must be created by the Wix account owner, not a contributor.
Read the guide → ReadyGoHighLevel
A sub-account Private Integration Token. White-label friendly, with the three things that must exist first.
Read the guide →On a different platform? Nina can publish anywhere with a writable API, and we have built one-off integrations before. Tell us what you run at tech@trynina.co and we will tell you honestly whether it is a clean fit.
The same four steps, whatever you run
The menus differ. The shape does not.
Create a credential
A dedicated user, app or token that exists only for Nina, so nothing is shared with your own login.
Grant the narrow set
Blog posts and images. Every guide lists the exact permissions and explains why each one is needed.
Check it works
Each guide has a copy-paste command that confirms the credential before you send it, so nothing bounces back.
Send it securely
A password manager share link is ideal. We confirm receipt and run a test post before anything real goes out.
What the credential can and cannot do
What Nina uses it for
- Create and edit blog posts
- Publish on the agreed schedule, or leave everything in drafts if you prefer
- Upload post images to your own media library, so they are served from your domain
- Read your published posts, so new ones link into the ones already earning traffic
- Update a ranking post in place rather than publishing a duplicate against it
What it will never touch
- Customers, orders, payments or any commercial data
- Products, pricing, inventory or discounts
- Themes, plugins, apps or site settings
- Your users, staff or their logins
- Deleting or unpublishing anything your team wrote
Most of that is enforced by the platform, not by our good intentions. On every CMS above, the permissions we ask for cannot reach your commercial data even if someone tried. Where a limit is a promise from us rather than a technical wall, the individual guide says so plainly instead of glossing over it.
You can end it in one click
Every method in these guides is revocable on its own, without changing your password, without affecting anyone else on your team, and without touching a single post we have already published. Revoke it and publishing simply stops. Your content stays exactly where it is, because it was always yours and it always lived on your platform.
Each guide ends with the exact revoke path for that CMS, and with where to look in your own admin to see everything Nina has done.
Stuck on any of it?
Send us the error, the screen you are on, or just your site URL. We set these up every week and can usually name the cause on the first reply.