<!-- BusyBot node reference — https://busybot.net/tools/twilio-trigger/ -->

> Node: Twilio Trigger (`twilio_trigger`) · Webhook trigger · v1
> Category: Communication · Credentials: Twilio (`twilioApi`)
> Updated: 2026-08-16

# Twilio Trigger

> Trigger workflows on Twilio SMS and voice events

## Overview

The Twilio Trigger node starts a workflow when events occur on your Twilio account. It uses the Twilio Event Streams API to subscribe to inbound SMS messages and completed voice call summaries. When Twilio detects a matching event, it sends the event payload to this webhook. Supports two event types: new inbound SMS messages and completed call summaries (note: call summaries may take up to 30 minutes to arrive). Outputs the full event payload as received from Twilio Event Streams.

**Category:** Communication  
**Tool Name:** `twilio_trigger`  
**Version:** 1

**Appearance:** Icon: `lucide-Phone` | Color: `#f22f46`

## Node Type

**Trigger** — webhook (receives incoming HTTP callbacks)

## Input / Output

| Direction | Port(s) |
|-----------|--------|
| Input | None (trigger node) |
| Output | `Output` |

## Credentials

This tool requires **Twilio** credentials.
See the [Credentials Guide](https://busybot.net/credentials/twilio-api/) for setup instructions.

### Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Trigger On | `multiOptions` | Yes | `[]` | Which Twilio events to listen for. |
| | | | | Options: `com.twilio.messaging.inbound-message.received` (an SMS message is received), `com.twilio.voice.insights.call-summary.complete` (a call summary is complete) |
| Verify Webhook Signature | `boolean` | No | `true` | Whether to verify the X-Twilio-Signature header using HMAC-SHA1 with the credential Auth Token. Required for standard Twilio webhooks (SMS/voice). Event Streams deliveries are not signed by Twilio; if you are using Event Streams exclusively, disable this option. |

## Output Data

Each accepted delivery produces one output item containing the full Twilio payload exactly as it arrived — the Event Streams event fields for Event Streams deliveries, or the form-encoded parameters for a standard SMS or voice callback — plus:

- `_trigger` — always `twilio_webhook`
- `_timestamp` — ISO 8601 timestamp of when the delivery was received
- `_webhookEvent` — the payload's `type` field, falling back to `EventType`, or `unknown` when neither is present

Reference the payload downstream by expression, e.g. `{{ $json.Body }}` for a standard SMS callback.

## Usage Examples

- Start a workflow when an SMS message is received on a Twilio number
- Trigger a support ticket flow when a customer sends a text
- Log all completed voice calls to a spreadsheet
- Send an auto-reply when an inbound SMS arrives
- Route incoming SMS messages to different teams based on content

## Example Configuration

Inbound SMS only:

```json
{
  "id": "twilio-sms-trigger",
  "type": "twilio_trigger",
  "typeVersion": 1,
  "position": [250, 300],
  "parameters": {
    "updates": ["com.twilio.messaging.inbound-message.received"],
    "verifySignature": true
  }
}
```

Completed call summaries, delivered through Event Streams — signature verification is turned off because Event Streams deliveries are unsigned:

```json
{
  "id": "twilio-call-trigger",
  "type": "twilio_trigger",
  "typeVersion": 1,
  "position": [250, 300],
  "parameters": {
    "updates": ["com.twilio.voice.insights.call-summary.complete"],
    "verifySignature": false
  }
}
```

Both SMS and call events in one workflow:

```json
{
  "id": "twilio-communication-trigger",
  "type": "twilio_trigger",
  "typeVersion": 1,
  "position": [250, 300],
  "parameters": {
    "updates": [
      "com.twilio.messaging.inbound-message.received",
      "com.twilio.voice.insights.call-summary.complete"
    ],
    "verifySignature": false
  }
}
```

### Trigger Behavior

- **Activation:** When the workflow is activated, a webhook endpoint is registered with the service.
- **Deactivation:** The webhook is automatically unregistered when the workflow is deactivated.
- **Payload:** The incoming webhook payload is parsed and output as workflow items.
- **Verification:** Supports signature verification where applicable.

## Tips

The Twilio Trigger listens for events from your Twilio account via the Event Streams API. Select which events to listen for: inbound SMS messages, completed call summaries, or both. When a matching event occurs, the workflow starts with the full event payload from Twilio. Note: The "New Call" event uses call summaries which may take up to 30 minutes to arrive.

### Important Notes

- The `updates` parameter is required and must contain at least one valid Twilio event type
- The "New Call" event may take up to thirty minutes to be triggered, because it is based on call summaries
- Multiple event types can be selected simultaneously to create workflows that respond to different types of Twilio events
- This trigger serves as the entry point for workflows, so it should typically be the first node in your workflow configuration
- Leave **Verify Webhook Signature** on for standard SMS and voice callbacks; turn it off only when every delivery comes from Event Streams, which Twilio does not sign