EZ Texting
Send SMS and MMS, manage contacts and groups, read the inbox, and subscribe webhooks on EZ Texting.
About
EZ Texting ships in the w6w first-party pack. It declares 31 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.eztexting- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Communication · Marketing
Overview
EZ Texting is a business text-messaging platform, and this app covers the messaging surface a workflow actually drives: sending an SMS or MMS to phone numbers or contact groups now or at a scheduled time, listing and deleting messages, reading a sent message’s recipients and credit cost, pulling its delivery, engagement and link-click report, and blocking outbound texts to a number.
Around the send it manages the audience: contacts (list, look up by phone number, create-or-update, batch import, delete) and contact groups (list, get, create, rename, delete, add and remove members), plus the media files used for MMS (created from a URL), the keywords an account has purchased (list, read settings, check availability), and the two-way inbox (list conversations and read one conversation’s messages).
It also reads the account’s credit balance, and subscribes webhooks to inbound texts, keyword opt-ins and new contacts so workflows can react to replies.
Health checks report EZ Texting’s own status page, anchored on its dedicated “EZ Texting API” component, and the account’s remaining credit balance alongside the credential check derived from the connection.
Build with EZ Texting
Three routes to the same 31 actions. The Workflow tab is generated from EZ Texting'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.
Create or Update Contacts (Batch)
contact-batch-upsert Create or update a batch of contacts, optionally adding them all to groups.
List Contacts
contact-list List contacts, filtered by phone number, name, email, group, source or opt-out.
Create or Update Contact
contact-upsert Create a contact, or update it if the phone number already exists.
List Conversations
conversation-list List inbox conversations with their last message and unread count.
List Conversation Messages
conversation-message-list List the messages in one conversation (the replies thread with a contact).
Create Contact Group
group-create Create a contact group, optionally seeded with numbers or other groups.
Remove Contacts from Group
group-remove-contacts Remove contacts, by phone number, from a contact group.
Get Message Details
message-details-get Get who a sent message went to, its credit cost and its sending number.
List Messages
message-list List sent and received messages, filtered by number, direction, type or date.
Get Message Report
message-report-get Get the delivery, engagement and link-click report for a sent message.
Send Message
message-send Send an SMS or MMS to phone numbers and/or contact groups, now or scheduled.
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 EZ Texting's real ids.
{
"manifestVersion": "2",
"name": "eztexting-example",
"steps": [
{
"id": "contact-batch-upsert",
"uses": {
"app": "io.w6w.eztexting",
"action": "contact-batch-upsert",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"contacts": "<contacts>"
}
}
]
}Here are some of the things you can do
-
Create or Update Contacts (Batch)
performcontact-batch-upsert -
Get Contact
readcontact-get -
List Contacts
searchcontact-list -
Create or Update Contact
performcontact-upsert -
List Conversations
searchconversation-list
+26 more actions available
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 EZ Texting, 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 EZ Texting. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { 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: "contact-batch-upsert",
payload: {
contacts: "<value>",
// groupIdsAdd: "<value>",
// groupIdsRemove: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action contact-batch-upsert --payload '{"contacts":"<value>"}'Give an AI agent EZ Texting — without giving it EZ Texting'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.eztexting#contact-batch-upsert",
"input": {
"contacts": "<contacts>"
}
}
}
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 EZ Texting 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
EZ Texting'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. EZ Texting itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
EZ Texting declares its own checks, so its health is a property of the app rather than something the host guesses at.
EZ Texting API status
Component status from status.eztexting.com, anchored on its dedicated "EZ Texting API" component. The SMS/MMS pipeline components are reported alongside but do not decide the verdict, and neither do CallFire's.
Credit balance
The account's remaining credits (plan + anytime), read from GET /v1/credits. Sending stops at zero rather than slowing down, so this reports exhausted vs. not.