n8n Autoposting Error

Short answer: No — the WordPress theme (Twenty Twenty-Three) is almost certainly not the cause. This is an authentication/permission/REST-access problem, not a theme issue. Themes control front-end appearance; REST API and user capabilities control whether the WordPress node in n8n can list users or create posts.

Here’s the tight, high-impact diagnosis and what to do next (follow in order):

Why theme ≠ culprit (fast)

• Themes rarely, if ever, block /wp-json/* or change authentication behavior.
• Your error text — “you are not allowed to create posts as this user” and “Error fetching options from WordPress” — points to auth/permission or a security layer rejecting REST calls, not to templates or themes.

What is likely wrong (ranked)

1. Wrong auth method (you used a login password instead of an Application Password or token).
2. The WP user lacks the capability (Author/Editor/Administrator).
3. REST API blocked by a security plugin, host firewall, Cloudflare or ModSecurity.
4. URL/HTTPS mismatch or redirect chain breaking auth.
5. Using WordPress.com/Jetpack when you set up self-hosted credentials (or vice versa).

Do this now — exact steps (no fluff)

1. Create an Application Password
   WP Admin → Users → Profile of the user you want n8n to act as → Application Passwords → name it → Generate → copy it.
2. Update n8n WordPress credential
   • Site URL: https://your-site.com (exact; include https://; no trailing space)
   • Username: the WP username (not email)
   • Password: paste the Application Password string you copied
     Save and test.
3. Quick curl tests (run from the same network as n8n — ideally the n8n server)
   Replace SITE, USER, APP_PASS and run: curl -i -u "USER:APP_PASS" "https://SITE/wp-json/wp/v2/users?context=edit"
   • If you get HTTP 200 + JSON users: auth works for listing users.
   • If you get 401/403: WP is rejecting auth.
   Then test creating a post: curl -i -u "USER:APP_PASS" -H "Content-Type: application/json" \ -d '{"title":"curl test","content":"hello","status":"draft"}' \ "https://SITE/wp-json/wp/v2/posts"
   • Expect 201 (created) or a JSON post object. 401/403 means permission/auth error.
4. If curl from your laptop works but n8n still fails
   • The n8n server IP might be blocked by a security plugin or host firewall. Either:
     • SSH to the n8n server and run the same curl there, or
     • Temporarily disable security plugins (Wordfence/Sucuri) and test, or whitelist the n8n server IP.
5. If curl fails (401/403)
   • Confirm the WP user role has Author/Editor/Admin. Temporarily test with an Admin account + new app password. If Admin works, it’s a role capability issue — either give the service user Author role or keep Admin for the service user (safer: create a dedicated Author user with the right capability).
6. Check URL/redirects & Cloudflare
   • Ensure the Site URL in WP Settings exactly matches the n8n credential URL (https, www vs non-www).
   • If you use Cloudflare, temporarily pause it or grey-cloud the DNS to test — some Cloudflare rules block POST to /wp-json/*.

About Elementor / “Elementor Template” toggle in your screenshot

• That toggle and template fields only affect how the post renders in Elementor; they do NOT affect authentication. Fix auth first—then worry about saving the Elementor meta if needed.

If you want me to give the exact curl command filled with values I can read from your screenshot (I see aiautomationbd.xyz earlier) — tell me to use that domain and I’ll paste the exact commands to run. Or paste the exact curl response body/status here and I’ll interpret it and give the one surgical next step (whitelist, role change, or URL fix).

Bottom line: Fix auth (Application Password + correct role) and verify with curl from the n8n host. Once that passes, the Author dropdown and post creation will populate and work.