Short.io
Create, update, list and delete Short.io branded short links, and read the domains, tags, folders and QR codes around them.
About
Short.io ships in the w6w first-party pack. It declares 18 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.short-io- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Developer Tools
Overview
Short.io is a branded link shortener: every short link lives on a domain you own, so a workflow can mint links like go.example.com/spring instead of a generic shared host.
This app covers the link lifecycle end to end: create a link (or up to 1,000 in one call), look one up by its id or by its domain and path, update where it points, archive or unarchive it, duplicate it, and delete it singly or in bulk. It also lists the links on a domain with cursor pagination, and reads the account’s domains, the tags used on a domain, and its link folders.
A workflow can also ask Short.io to render a QR code for any link. Health checks track Short.io’s own status page, which names the API as its own component.
Build with Short.io
Three routes to the same 18 actions. The Workflow tab is generated from Short.io'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.
Expand Link
link-expand Look a link up by its domain hostname and path, e.g. go.example.com and /spring.
Create QR Code
qr-code-create Generate a QR code for a link and return Short.io's JSON answer (a hosted URL).
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 Short.io's real ids.
{
"manifestVersion": "2",
"name": "short-io-example",
"steps": [
{
"id": "domain-get",
"uses": {
"app": "io.w6w.short-io",
"action": "domain-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"domainId": "<domainId>"
}
}
]
}Here are some of the things you can do
-
Get Domain
readdomain-get -
List Domains
searchdomain-list -
Create Folder
performfolder-create -
Get Folder
readfolder-get -
List Folders
searchfolder-list
+13 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 Short.io, 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 Short.io. 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: "domain-get",
payload: {
domainId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action domain-get --payload '{"domainId":"<value>"}'Give an AI agent Short.io — without giving it Short.io'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.short-io#domain-get",
"input": {
"domainId": "<domainId>"
}
}
}
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 Short.io 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
Short.io'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. Short.io itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Short.io declares its own checks, so its health is a property of the app rather than something the host guesses at.
Short.io platform status
cState status page at shortiostatus.com: the API component decides the verdict; Redirects, Dashboard, Landing page and Statistics are reported as components. Unauthenticated.