# Landbot integrations: customers and messages

> Send a text message, assign customer to agent and create a field in Landbot, and start a workflow when Landbot sends “Customer message”.

**Canonical page:** https://tray.ai/connectors/landbot-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

Landbot is a no-code chatbot builder for websites and WhatsApp, letting teams design conversational flows and hand chats to human agents. Tray.ai connects to Landbot through the HTTP Connector, so your workflows can call the Landbot API alongside the rest of your stack.

## Use cases

### Customers

Read and delete customers in Landbot from any Tray.ai workflow. The Landbot API covers calls such as list customers and get a customer.

- List customers
- Get a customer
- Archive a customer

### Messages

Read and create messages in Landbot from any Tray.ai workflow. The Landbot API covers calls such as send a text message and send an image.

- Send a text message
- Send an image
- Send a WhatsApp template

### Assignments

Update assignments in Landbot from any Tray.ai workflow. The Landbot API covers calls such as assign customer to agent and assign customer to bot.

- Assign customer to agent
- Assign customer to bot
- Unassign a customer

### Customer fields

Read, create, update, and delete customer fields in Landbot from any Tray.ai workflow. The Landbot API covers calls such as get a field and create a field.

- Get a field
- Create a field
- Update a field

### Channels

Read channels in Landbot from any Tray.ai workflow. The Landbot API covers calls such as list channels and get a channel.

- List channels
- Get a channel
- List WhatsApp templates

### Message hooks

Read, create, update, and delete message hooks in Landbot from any Tray.ai workflow. The Landbot API covers calls such as list message hooks and create a message hook.

- List message hooks
- Create a message hook
- Update a message hook

## Challenges Tray.ai solves

### Keeping Landbot credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Landbot credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Landbot API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Landbot API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Landbot?

Yes. Tray.ai connects to Landbot through the HTTP Connector, which calls the Landbot API directly. Any call the Landbot API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Landbot?

The Landbot API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Landbot connector?

Landbot runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Landbot connector from the Landbot API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/