LandinChat’s External HTTP API integration allows your chatbot to talk to external systems in real time—CRMs, WordPress, WooCommerce, payment gateways, internal tools, or any REST API.

This is what turns your chatbot from a “message sender” into a real automation system.

If you’re not using HTTP APIs, your bot is isolated and limited.

What Is HTTP API Integration in LandinChat? #

HTTP API integration lets your bot:

• Send data to external systems (POST)
• Fetch data from external systems (GET)
• Update records in real time
• Use API responses inside conversations

Examples:

• Create a user in WordPress
• Fetch WooCommerce products
• Check order status
• Push leads into CRM
• Validate coupon codes
• Trigger internal workflows

This is server-to-server automation, not gimmicks.

What You Can Build with HTTP API Integration #

Real, practical use cases:

• Show live WooCommerce product data inside chat
• Create or update users in WordPress
• Push leads to CRM (Zoho, HubSpot, custom)
• Fetch order/payment status dynamically
• Store chatbot inputs in your backend
• Trigger internal APIs based on user actions

If it has an API, LandinChat can connect to it.

How to Set Up an HTTP API Integration in LandinChat #

Step 1: Access HTTP API Settings #

1. Log in to LandinChat Dashboard
2. Go to Integrations → HTTP API
3. Click Create

Step 2: Add API Connection Details #

Fill in the basics:

• API Name
  Use something descriptive
  Example: wordpress_user_create
• HTTP Method
  Choose based on API:
  • GET → fetch data
  • POST → create data
  • PUT / PATCH → update data
  • DELETE → remove data
• Endpoint URL
  Example:
  https://example.com/wp-json/custom/v1/create-user

Step 3: Add Test Subscriber ID (Mandatory) #

• Copy a Subscriber ID from Subscriber Manager
• Paste it into Test Subscriber ID

This is required to:

• Test dynamic variables
• Validate API requests properly

Skipping this breaks testing.

Step 4: Configure Request Headers #

Common headers:

• Content-Type: application/json
• Authorization: Bearer YOUR_API_TOKEN

Headers depend entirely on the external API.
If auth fails, nothing works—don’t guess.

Step 5: Configure Request Body (If Required) #

For POST / PUT requests:

• Add required fields (e.g., name, email, phone)
• Choose value type:
  • Static → fixed value
  • Dynamic → user input / custom field

Select request format:

• JSON (most common)
• Form Data
• x-www-form-urlencoded

Match the API spec exactly. APIs don’t forgive mistakes.

Step 6: Verify & Save #

1. Click Verify Connection
2. If the response is successful → click Save API

If verification fails:

• Check endpoint
• Check headers
• Check request body
• Check auth token

Don’t move forward until this works.

Mapping API Response Data (Critical Step) #

Once the API responds, you can:

• Map response fields to subscriber custom fields
• Store values like:
  • user_id
  • order_id
  • status
  • product list

You can also:

• Save full response as JSON
• Use it later in interactive messages or logic

No mapping = wasted API call.

Using HTTP API Inside Bot Flow #

After setup:

1. Open Bot Flow Builder
2. Drag HTTP API Element into the flow
3. Select the API you created
4. Decide when it should run:
   • After user input
   • On button click
   • Before showing results

API calls should be intentional, not random.

Best Practices (Ignore These = Broken Bots) #

• Never hardcode sensitive tokens in messages
• Always validate user input before API calls
• Handle failed responses gracefully
• Don’t call APIs unnecessarily
• Log and test with real data before going live

Bad API logic will break your entire flow.

Key Takeaway #

HTTP API integration is what separates:

“Chatbots”
from
Automation systems

If your bot doesn’t connect to external systems, it’s not automation—it’s just scripted replies.

Frequently Asked Questions (FAQs) #

1. Do I need coding knowledge to use HTTP API? #

Basic API understanding helps, but no heavy coding is required.

2. Can I connect WooCommerce or WordPress? #

Yes. Both work perfectly via REST APIs.

3. Can I send user input to my backend? #

Yes. Dynamic values can be passed from chatbot inputs.

4. What happens if the API fails? #

The flow continues unless you add logic to handle failures. You should handle errors explicitly.

5. Can I store API responses in custom fields? #

Yes. You can map response fields directly to subscriber data.

6. Is authentication supported? #

Yes. Token-based, header-based, and custom auth methods are supported.

7. Can I call multiple APIs in one flow? #

Yes, but be careful with execution order and delays.

8. Does this work in WhatsApp and Webchat? #

Yes. API logic is channel-agnostic.

9. What’s the most common mistake? #

Not verifying the API before using it in a live flow.

10. Who should use HTTP API integration? #

Anyone doing:

• eCommerce
• CRM syncing
• Payments
• Advanced lead handling
• Custom workflows