Connectors: Integrations with External Systems

Connect Your Agent to APIs and Real-Time Data

What Are Connectors?

Connectors allow your agent to call external APIs to access real-time data from your systems:

• CRM (Salesforce, Zoho CRM, HubSpot)
• Calendars (Google Calendar, Outlook, Calendly)
• Inventory (Shopify, WooCommerce)
• Billing (SAP, NetSuite, Odoo)
• Support (Zendesk, Freshdesk, Jira)
• Custom databases

Result: The agent responds with up-to-date information from your real systems.

Example Without Connector

Customer: "What's the status of my order #12345?"
Agent: "I'll check your order. Orders take 3-5 days."

Example WITH Connector

Customer: "What's the status of my order #12345?"
[Agent calls your inventory API]
Agent: "Your order #12345 shipped today from the warehouse. 
It will arrive tomorrow between 2-5 PM. Tracking: TR123456789"

Connector Structure

Every Connector needs 4 parts:

1. Base URL

Your API domain:

https://api.yourcompany.com

2. Authentication

How your API validates requests:

Option 1: API Key

Header: Authorization: Bearer sk_live_abc123def456

Option 2: OAuth

Requires login. Meta handles the flow automatically.

Option 3: Basic Auth

Header: Authorization: Basic base64(user:password)

3. Tools (Endpoints)

The actions the agent can perform:

GET /orders/{order_id}  → Get order status
GET /customers/{email}  → Get customer data
POST /tickets          → Create support ticket
GET /inventory         → Check stock

4. Parameters

The data the agent sends to each endpoint:

GET /orders/{order_id}
Parameters:
  - order_id (required) → Order ID
  - format (optional)   → json/xml

Use Cases by Industry

E-commerce

Connector: Inventory + Orders

Endpoints:

• GET /products/{sku} → Available stock
• GET /orders/{order_id} → Shipping status
• GET /tracking/{order_id} → Tracking number
• POST /returns → Create return

Benefit: Customer gets real answer in 2 seconds with no intermediaries.

SaaS

Connector: CRM + Account Data

Endpoints:

• GET /accounts/{email} → Account info
• GET /subscriptions/{account_id} → Current plan
• GET /usage/{account_id} → Monthly usage
• POST /support-tickets → Create ticket

Benefit: Tech support without manual access to systems.

Services

Connector: Calendar + CRM

Endpoints:

• GET /availability → Available times
• POST /bookings → Create appointment
• GET /clients/{phone} → Client history
• PUT /clients/{client_id} → Update info

Benefit: Agent schedules appointments without human intervention.

How to Create a Connector

Step 1: Go to Advanced › Connectors

In WOZTELL:

Channels
→ Your channel
→ Meta AI Agent
→ Scroll down
→ "Advanced"
→ "Connectors"

Step 2: Click "Add Connector"

Step 3: Enter Base URL

https://api.yourcompany.com

Step 4: Choose Authentication Method

API Key (Recommended for simple APIs)

Type: API Key
Location: Header (Bearer)
Key: sk_live_abc123def456

OAuth (For complex systems like Salesforce)

Requires OAuth credentials already in your API
WOZTELL handles the flow automatically

Basic Auth

Username: your_user
Password: your_password

Step 5: Add Tools (Endpoints)

Click "Add Tool" for each endpoint the agent can use:

Example:

Tool 1: Get Order Status
Method: GET
Path: /orders/{order_id}
Parameters:
  - order_id (string, required)

Tool 2: Get Product Stock
Method: GET
Path: /products/{sku}/stock
Parameters:
  - sku (string, required)

Step 6: Test

WOZTELL should let you make a test call:

GET /orders/123
Response: {
  "order_id": "123",
  "status": "shipped",
  "tracking": "TR123456789"
}

Step 7: Save

The Connector appears in the list. Now Skills can use it.

Using a Connector in a Skill

Once the Connector is configured, Skills can access it:

Example: Skill "Check Order Status"

Name: "Check Order Status"

When to use it:
"When customer asks about their order status or tracking"

What the agent should do:
"1. Ask for the order ID if not provided
2. Call the Connector: GET /orders/{order_id}
3. Respond with status and tracking number
4. If shipped, mention estimated delivery date"

Meta Business Agent automatically:

1. Extracts the order ID from the conversation
2. Calls the Connector
3. Receives the response in JSON
4. Integrates the data into the agent's response

HTTP Methods

Real-World Examples

Example 1: Shopify (E-commerce)

API Base:

https://your-store.myshopify.com/admin/api/2023-04

Authentication:

API Key in header:
Authorization: Bearer your_access_token

Tools:

1. GET /products/{id}.json
   → Get product details

2. GET /orders/{id}.json
   → Get order status

3. POST /fulfillments/{order_id}.json
   → Update shipping status

Example 2: Google Calendar

API Base:

https://www.googleapis.com/calendar/v3

Authentication:

OAuth (Google provides access token)

Tools:

1. GET /calendars/{calendar_id}/events
   → Get today's events

2. POST /calendars/{calendar_id}/events
   → Create event/appointment

Example 3: Zendesk (Support)

API Base:

https://your-domain.zendesk.com/api/v2

Authentication:

Basic Auth:
User: your_email@example.com
Password: your_api_token

Tools:

1. GET /users/search?email={email}
   → Search customer

2. POST /tickets
   → Create ticket

3. GET /tickets/{id}
   → Get ticket details

Important Limitations

⚠️ Rate Limits

Your API may have limits (e.g., 100 calls/minute). Monitor:

• How many calls the agent makes
• If you hit rate limits
• Implement queue if necessary

⚠️ Latency

API calls take time. If your API takes >5 seconds:

• Customer sees delay in response
• Poor experience
• Solution: Optimize your API or cache data

⚠️ Security

Never share credentials in chat or documents:

• API Keys are stored on WOZTELL servers (secure)
• Don't expose secrets in public Skills
• Use environment variables

⚠️ Sensitive Data

The agent might expose data that shouldn't be public:

Bad: "Your balance is $5,000 and your SSN is 123-45-6789"
Good: "Your balance is $5,000. Need changes? Contact support?"

Troubleshooting

Getting Started

Do you have an API ready?

1. Make sure it's HTTPS (not HTTP)
2. Document the available endpoints
3. Get authentication credentials
4. Contact soporte@woztell.com to set it up

Don't have an API?

1. Use platforms like Make or Zapier
2. Create webhooks that Connectors can call
3. Build a simple API (Python Flask, Node Express)

Need Help?

• Configure Connector: soporte@woztell.com
• Custom API: WOZTELL development team
• Integration with existing system: We evaluate feasibility