Log in Sign up
First-party app
Twilio

Twilio

Send SMS/MMS/WhatsApp messages and make phone calls via Twilio.

stable Communication

About

Twilio ships in the w6w first-party pack. It declares 2 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.

App id
io.w6w.twilio
Version
0.3.1
Author
w6w
Licence
MIT
Categories
Communication

Overview

Twilio sends messages and makes calls from a workflow — one action covers SMS, MMS and WhatsApp, switching between them by sender and destination rather than requiring three separate actions, with media attachments supported for MMS. A second action places an outbound phone call.

The messaging action supports both a plain phone number sender and a Messaging Service SID — the pooled-sender setup Twilio’s own A2P 10DLC registration attaches to — so a workflow can use whichever a Twilio account is actually configured with.

A fit for sending transactional notifications, appointment reminders or two-factor codes by SMS or WhatsApp, or triggering an automated outbound call as part of an alerting or reminder workflow.

Build with Twilio

Three routes to the same 2 actions. The Workflow tab is generated from Twilio's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Make Call

make-call

Place an outbound phone call with a spoken message or TwiML payload.

Send SMS

send-sms

Send an SMS, MMS, or WhatsApp message.

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying Twilio's real ids. 

{
  "manifestVersion": "2",
  "name": "twilio-example",
  "steps": [
    {
      "id": "make-call",
      "uses": {
        "app": "io.w6w.twilio",
        "action": "make-call",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "from": "<from>",
        "to": "<to>",
        "message": "<message>"
      }
    }
  ]
}

Here are some of the things you can do

  • Make Call

    perform
    make-call

  • Send SMS

    perform
    send-sms

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for Twilio, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to Twilio. The Workflow tab is where this app's real ids are.

Install 
npm install @w6w/sdk
yarn add @w6w/sdk
pnpm add @w6w/sdk
deno add npm:@w6w/sdk
Code 
import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "send-sms",
  payload: {
    // sender: "<value>",
    to: "<value>",
    message: "<value>",
    // toWhatsapp: "<value>",
    // sendOptions: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);
Install the CLI 
npm install -g @w6w/cli
CLI 
w6w run conn_YOUR_CONNECTION_ID --action send-sms --payload '{"to":"<value>","message":"<value>"}'

Give an AI agent Twilio — without giving it Twilio's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call 
{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.twilio#make-call",
    "input": {
      "from": "<from>",
      "to": "<to>",
      "message": "<message>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's Twilio connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

Twilio's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. Twilio itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

Twilio declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

Twilio platform status

Atlassian Statuspage rollup for status.twilio.com, with per-component detail. Unauthenticated and unsigned.

quota

API quota headroom