Salesmsg
Send business SMS and MMS, and manage contacts, conversations, tags, inboxes and numbers in Salesmsg.
About
Salesmsg ships in the w6w first-party pack. It declares 27 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.salesmsg- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Communication · Marketing
Overview
Salesmsg is a business texting platform: shared team inboxes, two-way SMS and MMS conversations, contact records with tags and custom fields, and CRM integrations. This app drives its public API (v2.3) with a Personal Access Token.
It covers the day-to-day surface a workflow needs: send a text to a phone number from a chosen inbox, or into an existing conversation (optionally scheduled, with media); list, search, create, update and delete contacts; opt contacts in and out; create tags and attach or detach them; list, open, close and assign conversations; read a conversation’s messages; and look up the organization, its members, inboxes (teams) and phone numbers.
Salesmsg is not a drop-in REST API in the usual sense: most writes take their fields in the query string rather than a JSON body, and list endpoints answer three different envelopes, which this app normalises to items and meta. Broadcasts, triggers, keywords, groups, voice, analytics, billing and the administrative surface (numbers purchase, team and member management, agency) are deliberately left out.
Health checks derive credential validity from the connection and state plainly that the vendor’s status page does not cover the API and that no quota is published.
Build with Salesmsg
Three routes to the same 27 actions. The Workflow tab is generated from Salesmsg'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.
Assign Conversation
conversation-assign Assign a conversation to a user, or leave the user blank to unassign it.
Send Message to Conversation
message-send-to-conversation Send an SMS or MMS into an existing conversation.
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 Salesmsg's real ids.
{
"manifestVersion": "2",
"name": "salesmsg-example",
"steps": [
{
"id": "contact-create",
"uses": {
"app": "io.w6w.salesmsg",
"action": "contact-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"number": "<number>"
}
}
]
}Here are some of the things you can do
-
Create Contact
performcontact-create -
Get Contact
readcontact-get -
List Contacts
searchcontact-list -
Opt In Contact
performcontact-opt-in -
Opt Out Contact
performcontact-opt-out
+22 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 Salesmsg, 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 Salesmsg. 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-create",
payload: {
number: "<value>",
// first_name: "<value>",
// last_name: "<value>",
// email: "<value>",
// phone_type: "<value>",
// source: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action contact-create --payload '{"number":"<value>"}'Give an AI agent Salesmsg — without giving it Salesmsg'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.salesmsg#contact-create",
"input": {
"number": "<number>"
}
}
}
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 Salesmsg 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
Salesmsg'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. Salesmsg itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Salesmsg declares its own checks, so its health is a property of the app rather than something the host guesses at.