# Twilio MMS

<!-- meta: type=twilio-mms; location=Messaging › Mobile; category=Step (action); platforms=Joomla and WordPress (where applicable) -->

## Overview

Sends an MMS message through Twilio with one or more public media URLs attached. Use for photo confirmations, receipts, or rich alerts that SMS alone cannot carry.

When the flow reaches this step, JOrchestrator executes **Twilio MMS** against your linked site or an external integration, using the field values you set on **General** and **Design**. Downstream steps can read the output payload fields defined for this node.

## Why use this node

Twilio MMS is a **action step** in the **Messaging › Mobile** group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add **Twilio MMS** to a flow:

- Send a photo or PDF receipt after an order completes
- Deliver rich alerts with product images from upstream media steps
- Attach proof-of-delivery images from field-service workflows

## Example workflows

Common patterns on the canvas:

1. **Trigger or Webhook** → upstream steps → **Twilio MMS** → **Send Email** or CMS update
2. **Scheduled trigger** → **Twilio MMS** → **Debug** (while testing) → production action

## How to set it up

Media URLs must be http/https and reachable by Twilio's servers. Optional message body text.

## Good to know

Use upload-media or a public CDN URL — localhost URLs will not work.

## Properties panel

The designer shows these tabs for this node:

| Tab | Purpose |
|-----|---------|
| **Info** | Plain-language description and output payload fields for downstream steps |
| **General** | Canvas label and read-only node ID |
| **AI** | Optional assistant to help draft settings from plain language |
| **Design** | Node-specific configuration fields |

### System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `_nodeId` | Node ID | `node-id` | No | — | — |
| `_payloadFields` | Available Fields | `payload-panel` | No | — | — |

### User-configured — General tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `label` | Label | `text` | No | — | Node label |

### User-configured — Design tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `to` | To | `payload-text` | **Yes** | — | +15551234567 |
| `from` | From (optional) | `payload-text` | No | — | Uses default from Joomla Node Configuration → Twilio if empty |
| `body` | Message (optional) | `textarea` | No | — | Caption text or {{node_id.field}} |
| `mediaUrls` | Media URLs | `textarea` | **Yes** | — | https://example.com/image.jpg (one per line or comma-separated) Public https URLs Twilio can fetch. At least one is required for MMS. |
| `statusCallback` | Status callback URL (optional) | `payload-text` | No | — | https://example.com/twilio/status |

### CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under **Node Configuration**, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

## Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as
`{{twilio_mms.success}}`.

| Field key | Type | Description |
|-----------|------|-------------|
| `success` | boolean | Whether the operation completed successfully. |
| `sid` | string | Twilio message SID. |
| `status` | string | HTTP status code or operation status string. |
| `to` | string | Recipient address or user. |
| `from` | string | Sender address or number. |
| `body` | string | Raw content — response text, file bytes (often base64), or message body. |
| `numMedia` | string | Number of media attachments (MMS). |
| `message` | string | Human-readable status, error, or result summary. |
| `mediaUrls` | array | Array of media URLs attached to the MMS. |
| `mediaCount` | number | Number of media attachments sent. |

## Validation rules

- **To** (`to`) must be filled before the flow can be saved.
- **Media URLs** (`mediaUrls`) must be filled before the flow can be saved.

## Related nodes

Other steps in the same area of the palette:

- **Discord Message** (`discord-message`) — Messaging › Social
- **Send Email** (`send-email`) — Messaging › Email
- **Send Notification** (`send-notification`) — Messaging › Notifications
- **Slack Message** (`slack-message`) — Messaging › Social
- **Twilio SMS** (`twilio-sms`) — Messaging › Mobile