FruxonDocs

Twilio

Twilio Programmable Messaging integration for sending and receiving SMS and WhatsApp messages

The Twilio integration lets your agents send and receive SMS and WhatsApp messages through a Twilio account. It's a credentials container that powers the participant dispatcher; no agent-facing tools are exposed yet.

Prerequisites

You need a Twilio account with:

  1. An Account SID and Auth Token from your Twilio Console.
  2. A verified sender phone number in E.164 format (e.g. +14155238886). For WhatsApp, this is the WhatsApp-enabled number on your account.
  3. A Messaging webhook URL configured in the Twilio Console on your number — point it at the webhook URL Fruxon generates for the participant binding (so inbound messages reach your agent).

Setup

  1. Open Integrations and select Twilio.
  2. Click Add Integration Config.
  3. Give the config a display name (e.g., "Twilio — Support Line").
  4. Paste your From Number (E.164, e.g. +14155238886). This is the verified sender used on every outbound message.
  5. Choose Account SID + Auth Token and paste:
    • Account SID (the username Twilio uses for HTTP Basic auth)
    • Auth Token (the password)
  6. Save the config.

Each Twilio number has a single Messaging webhook URL in the Twilio Console. Fruxon assigns one webhook per Twilio config; copy it into the Messaging → A MESSAGE COMES IN field for your number so inbound SMS / WhatsApp messages reach the dispatcher.

Channels

Twilio exposes a single channel descriptor:

ChannelDescription
smsA phone-number conversation — SMS or WhatsApp, identified by an E.164 phone number (e.g. +14155238886).

Bind participants to a Twilio channel under Network → Participants to let your agents reach a contact by phone or WhatsApp.

Triggers

TriggerDescription
twilio.message.receivedFires when an SMS or WhatsApp message arrives at the configured Twilio number. Requires the Twilio webhook to be registered against this tenant's Fruxon ingress.

The trigger payload includes the standard inbound-message fields (payload.text, payload.from, payload.from_name, payload.conversation_name, payload.conversation_address, payload.session_id, payload.event_type) plus Twilio-specific fields:

  • payload.message_attributes.from — E.164 sender number.
  • payload.message_attributes.to — E.164 Twilio number the message arrived at.

Available Tools

No tools yet. This integration currently exists as a credentials container for the outbound message dispatcher. Tool support (send SMS, list messages, etc.) will land in a follow-up.

On this page