Connecting your website (WordPress, embed widget, or content API)
For NexoFlow to publish blog posts to a website, it needs a way to deliver them. There are three supported delivery methods. You pick one per project.
What it is
For NexoFlow to publish blog posts to a website, it needs a way to deliver them. There are three supported delivery methods. You pick one per project.
- 1. WORDPRESS- Posts are pushed straight into the WordPress site.
- 2. EMBED WIDGET- You paste one snippet of code into the site and posts appear.
- 3. CONTENT API- A developer pulls posts into a custom-built site.
Social-only projects skip this entirely.
Where to find it
Sidebar > System > Website Integration (also reachable from the project itself under Projects > All Projects)
Option 1: WordPress
The simplest option if the site runs WordPress. NexoFlow creates real posts in WordPress, with the title, body, tags, categories, SEO fields and featured image.
Two ways to connect
A) wordpress.com
If the site is hosted on WordPress.com (or connected through Jetpack), use "Connect with WordPress.com". You sign in with WordPress and approve access. No passwords to copy.
B) APPLICATION PASSWORD (self-hosted WordPress) This is the standard method for self-hosted WordPress sites.
IMPORTANT: use an Application Password, NOT your normal WordPress login password. An Application Password is a separate credential WordPress creates for connecting apps, and it can be revoked at any time without changing your own password.
To create one: 1. Log in to WordPress as an administrator. 2. Go to Users > Profile (in some versions: Users > Your Profile). 3. Scroll down to "Application Passwords". 4. Give it a name, e.g. "NexoFlow", and create it. 5. Copy the generated password immediately- WordPress only shows it once. 6. Paste it into NexoFlow along with your WordPress site URL and username.
Requirements
- WordPress 5.6 or newer (Application Passwords were added in 5.6).
- The site must be reachable over HTTPS from the internet.
- The user account must have permission to publish posts.
- The WordPress REST API must not be blocked. Some security plugins and hosts disable it by default.
Option 2: embed widget (non-wordpress sites, no developer needed)
Best when the site is not WordPress and you do not have a developer available.
You copy one small snippet from NexoFlow and paste it into the page where the blog should appear. From then on, published posts show up there automatically- no further work per post.
What you can control
Posts per page Up to 50
- Theme- Light, dark, or automatic (follows the visitor's own setting)
- Layout- List or grid
- Show images- On or off
- Show dates- On or off
- Show excerpts- On or off
- Accent colour- A specific colour, or inherit from your page
- Date language- A specific locale, or follow the visitor's browser
- Base path- e.g. /blog- used to build the URL of each individual post
- Status- Live, or draft. Draft means the widget renders nothing at all, which is useful while you are still setting the page up.
NexoFlow can tell you whether the snippet is actually installed. The Website Integration page shows an install check, and it also records when the widget was last seen live on your site.
Option 3: content API (for developers)
If the site is custom-built and you have a developer, they can pull published posts directly from NexoFlow's Content API and render them however the site requires.
The Website Integration page generates a per-project integration snippet and the API key. content api and sdk for the developer detail.
Which should i choose?
Site is WordPress ....................... WordPress Site is not WordPress, no developer ..... Embed widget Site is custom-built, have a developer .. Content API No website at all ....................... Social-only project, skip this
A WordPress project always publishes by pushing into WordPress. The widget is not used on WordPress projects, because the posts are already on the site and the widget would show a duplicate copy of them.
Connection status
NexoFlow tracks the health of the website connection and shows a status. The meanings:
- Not connected- No delivery method set up yet.
- Checking- A connection test is running.
- Connected- Verified and working.
- Needs WordPress auth- WordPress credentials are missing, wrong or revoked.
- Needs setup- The delivery method is chosen but not finished (for example the widget snippet is not on the site).
- Wrong type- The site does not look like the type selected.
- Publish test failed- The credentials were accepted but a test publish did not succeed.
Common questions
How do I connect my WordPress site?
Use an Application Password created in WordPress under Users > Profile > Application Passwords, and enter it with your site URL and username. If the site is on WordPress.com, use the "Connect with WordPress.com" button instead.
It is asking for an "Application Password". Is that my WordPress password?
No. It is a separate credential you create inside WordPress specifically for connecting apps. Your normal password will not work, and should not be used.
My site isn't WordPress. Can I still publish blog posts to it?
Yes- either paste the embed widget snippet into your site, or have a developer pull posts from the Content API.
Do I need a developer?
Not for WordPress, and not for the embed widget. Only the Content API option requires development work.
Where do I put the embed snippet?
On the page where the blog should appear, in the place you want the list of posts to render. Your web builder or developer can paste it into a custom HTML / code block.
I pasted the snippet but nothing shows.
Check that the widget status is set to Live, not Draft- Draft deliberately renders nothing. Then confirm you have at least one published post, and that the snippet is actually on the live page rather than an unsaved draft of it.
Can I change delivery methods later?
Yes. A Social-only project can be turned into a website project, and a website project can move between the widget and the Content API.
Is my WordPress password stored?
NexoFlow stores an Application Password, not your login password, and it is encrypted. You can revoke it from WordPress at any time, which immediately cuts off access without affecting your own login.
Troubleshooting
SYMPTOM: WordPress connection fails
- Confirm the site URL is exactly right, including https:// and any subpath.
- Confirm you used an Application Password, not the account password.
- Confirm the username is the WordPress username, not the email address, if the site is picky about it.
- Check WordPress is version 5.6 or later.
- Check that a security plugin, WAF or host setting is not blocking the WordPress REST API. This is the single most common cause.
- Confirm the user has permission to publish posts.
SYMPTOM: Status says "Publish test failed"
The credentials worked but posting did not. Usually a permissions problem on the WordPress user, or a plugin intercepting post creation.
SYMPTOM: Posts publish in NexoFlow but never appear on the site
- For WordPress: check whether posts are landing as drafts in WordPress.
- For the widget: confirm the snippet is on the live page and the widget is set to Live.
- For the Content API: the site has to actually re-fetch. A cached or statically-built site may need a rebuild or cache purge.
SYMPTOM: Widget shows old posts
Your site or CDN may be caching the page. Purge the cache.