TextMagic
Send and schedule text messages, and manage contacts, lists, templates and two-way conversations, via the TextMagic REST API v2.
About
TextMagic ships in the w6w first-party pack. It declares 25 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.textmagic- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Communication · Marketing
Overview
TextMagic is a bulk SMS and business texting platform: send one-off or scheduled text messages, manage contacts and contact lists, save reusable message templates, and track two-way conversations (‘chats’) with recipients — all over TextMagic’s REST API v2.
This app covers the core messaging lifecycle: sending and scheduling messages (including recurring sends via iCal RRULE), reading delivery status, managing contacts and the lists that group them for targeting, creating message templates with merge fields, and reading chat history and scheduled-message state.
Health checks track TextMagic’s own status page — weighted on the SMS API Gateway and outbound-sending components this app actually depends on — alongside the account’s pre-paid balance, since sending stops outright at zero rather than degrading.
Build with TextMagic
Three routes to the same 25 actions. The Workflow tab is generated from TextMagic'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.
Update Contact
contact-update Edit a contact. Rate-limited to 5 requests/second, tighter than the account default.
Set List Contacts (replaces membership)
list-set-contacts Replace a list's members with exactly the given contact IDs. This REMOVES any existing member not included. Rate-limited to 5 requests/second.
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 TextMagic's real ids.
{
"manifestVersion": "2",
"name": "textmagic-example",
"steps": [
{
"id": "chat-get",
"uses": {
"app": "io.w6w.textmagic",
"action": "chat-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Chat
readchat-get -
Get Account
readaccount-get -
List Chats
readchat-list -
Get Chat Messages
readchat-messages-get -
Create Contact
performcontact-create
+20 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 TextMagic, 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 TextMagic. 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: "chat-get",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action chat-get --payload '{"id":"<value>"}'Give an AI agent TextMagic — without giving it TextMagic'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.textmagic#chat-get",
"input": {
"id": "<id>"
}
}
}
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 TextMagic 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
TextMagic'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. TextMagic itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
TextMagic declares its own checks, so its health is a property of the app rather than something the host guesses at.
TextMagic platform status
Component status from status.textmagic.com, weighted on the SMS API Gateway and Sending text messages (Outbound SMS) components — the two this app's traffic actually depends on.
Account balance
The account's pre-paid balance, read from GET /user. Sending stops at zero rather than slowing down, so this reports exhausted vs. not rather than a computed fraction.