Integrating LandinChat with WordPress using HTTP API allows you to automatically create WordPress user accounts directly from WhatsApp conversations. This is useful for SaaS onboarding, course access, gated content, or community platforms—without manual admin work.

This guide walks you through correctly configuring the WordPress API, authenticating securely, mapping chatbot data, and triggering user creation reliably.

Why This Integration Makes Sense (No Hype) #

Let’s be clear about the real benefits:

• Automation: No manual user creation in WordPress
• Instant onboarding: User gets access immediately after WhatsApp interaction
• Lower support load: No “please create my account” tickets
• Scales cleanly: Works for hundreds or thousands of users

If you’re not onboarding users at scale, this setup is overkill. Otherwise, it’s worth doing properly.

Step 1: Set Up the HTTP API in LandinChat #

Navigate to HTTP API #

From the left sidebar in LandinChat:

• Go to Integrations / Settings → HTTP API
• Click Create New API

Configure API Details #

Use the following settings:

• API Name: WordPress User Create
• Method: POST
• Endpoint URL: https://yourwebsite.com/wp-json/wp/v2/users

This is the official WordPress REST endpoint for user creation.

Step 2: Configure Authentication (Critical Step) #

WordPress does not allow anonymous user creation. Authentication is mandatory.

Generate WordPress Application Password #

1. Log in to WordPress Admin
2. Go to Users → Your Profile
3. Scroll to Application Passwords
4. Create a new password
   Example name: LandinChat API
5. Copy the generated password (you won’t see it again)

Encode Credentials (Base64) #

You must encode:

username:application_password

Example:

admin:abcd1234efgh5678

After Base64 encoding:

YWRtaW46YWJjZDEyMzRlZmdoNTY3OA==

You can use any Base64 encoder (CLI or online).

Add Headers in LandinChat #

Add both headers:

Header 1

• Key: Content-Type
• Value: application/json

Header 2

• Key: Authorization
• Value:

Basic YWRtaW46YWJjZDEyMzRlZmdoNTY3OA==

If this is wrong, nothing will work. No partial credit here.

Step 3: Map API Request Body #

In the Request Body, map WordPress-required fields.

Recommended Mapping #

{
  "username": "{{phone_number}}",
  "name": "{{full_name}}",
  "email": "{{email}}",
  "password": "Temp@12345",
  "roles": ["subscriber"]
}

Important Notes #

• username must be unique
• email must be valid
• Use subscriber, not admin/editor
• Password can be:
  • Static (simpler)
  • Dynamically generated (better security)

You can map values dynamically from chatbot inputs stored in custom fields.

Step 4: Verify the API Connection #

Click Verify Connection inside LandinChat.

If it fails:

• Check credentials
• Check endpoint URL
• Check WordPress REST API is not blocked by firewall or security plugins

Do not proceed until this passes.

Step 5: Create the Chatbot Flow #

1. Trigger the Flow #

• Create a keyword trigger like: register

2. Collect User Inputs #

Use User Input Flow to collect:

• Full Name
• Email Address

Store them in custom fields.

3. Confirmation Message #

Send a neutral message:

“Creating your account. Please wait…”

Avoid promising success before API execution.

4. Trigger HTTP API Action #

• Add HTTP API node
• Select your WordPress API
• Map custom fields to request body

5. Success Message #

Example:

“Your WordPress account has been created successfully.
Please check your email for login details.”

⚠️ Do NOT send passwords on WhatsApp in production systems. That’s sloppy security.

Step 6: Test the Integration #

Test end-to-end:

• Trigger chatbot
• Submit details
• Check WordPress → Users
• Verify correct role assignment
• Confirm duplicate users are handled properly

If WordPress returns a 409 error, the user already exists.

Security & Reality Checks (Read This) #

• Never use admin credentials
• Never expose API passwords in frontend JS
• Don’t auto-create users without consent
• Rate-limit bot triggers to avoid spam registrations

Automation done badly becomes a liability.

FAQs #

1. Can I create WordPress admins via this method? #

Technically yes. Practically stupid. Don’t do it.

2. What happens if the email already exists? #

WordPress rejects the request. Handle this gracefully in the chatbot.

3. Can I generate random passwords automatically? #

Yes. Recommended for security.

4. Is Application Password secure? #

Yes, if kept server-side and rotated periodically.

5. Can I assign WooCommerce customers automatically? #

Yes, by assigning the customer role instead of subscriber.

6. Does this work on shared hosting? #

Yes, unless security plugins block REST API access.

7. Can I trigger this after payment? #

Yes—and that’s the best use case.

8. Can I send login credentials on WhatsApp? #

Possible, but unsafe. Use email instead.

9. What if the API fails mid-flow? #

Always add a fallback message and alert an admin.

10. Is this suitable for large-scale onboarding? #

Yes, if rate-limited and properly monitored.