> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sendblue

> Answer iMessage, RCS and SMS through Sendblue

Sendblue lets the assistant answer an iMessage, RCS or SMS conversation from a Sendblue sender number. A customer texts that number and the reply goes back on the same service.

## When to use it

Use it when you already send Apple Messages or SMS through Sendblue and want the assistant in that thread. The sender number must be a Sendblue line in E.164 format, for example +15551234567.

## What the assistant hears

The assistant hears inbound messages delivered to a **receive** webhook. iMessage, SMS and RCS are the services this connection accepts.

## Where the keys come from

The linked provider guide shows the screens for these clicks. Follow the clicks below together with those pictures.

Copy the **API Key ID** and **API Secret Key** from the credentials screen in the Sendblue dashboard. You choose the webhook signing secret yourself, so it exists before the Famulor URL. The dashboard path for the webhook is documented, with the setup screens, in [Sendblue webhooks](https://docs.sendblue.com/getting-started/webhooks/): **Developer → Webhooks**, type **receive**. Sendblue sends the secret in the `sb-signing-secret` header.

## Create it at the provider

1. Sign in to the Sendblue dashboard.
2. Copy the API Key ID and the API Secret Key from the account credentials.
3. Copy the sender number in E.164 format.
4. Invent a webhook signing secret and keep it. You will paste the same value into Famulor and into the receive webhook.

## Connect it in Famulor

Your plan includes this channel. Open **Settings → Channels**, choose the card, name the connection, pick an assistant and save. The shared conversation settings — response delay (default 5 seconds) and inactivity timeout (default 30 minutes) — are described on the [messaging channels](https://docs.famulor.io/channels/messaging.md) page.

On the **Sendblue** card paste **Sendblue API Key ID**, **Sendblue API Secret Key**, **Sendblue sender number (E.164)** and **Webhook signing secret**.

After saving, open the connection menu and choose **Copy webhook URL**. Paste that exact address into the provider. A verified custom domain is already part of the address Famulor shows.

## Point the provider at Famulor

1. Copy the Famulor webhook URL.
2. In the Sendblue dashboard open **Developer → Webhooks**.
3. Add a webhook of type **receive**. Set the URL to the Famulor address and the secret to the value you saved in Famulor.
4. Text the sender number. The conversation appears in History.

## History

Open [History](https://docs.famulor.io/monitoring/history.md) and filter by **Sendblue**. The thread, the assistant reply and any analysis appear there. You can pause the assistant and answer manually.

## API, MCP and command line

The same connection can be created with the public API, the MCP tool `create_messaging_connector`, or the command line. Replace the placeholders with your own values.

```bash theme={null}
famulor create-messaging-connector --platform sendblue --name "Support" \
  --assistant-id ASSISTANT_UUID --api-key KEY_ID --api-secret KEY_SECRET --from-number +15551234567 --webhook-secret YOUR_SECRET
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.