Bitly
Shorten, manage and track Bitly links via the Bitly REST API v4.
About
Bitly ships in the w6w first-party pack. It declares 8 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.bitly- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Analytics & BI
Overview
Bitly turns link management into a workflow step — shorten a URL, look one up, update its destination, and pull click analytics, all through Bitly’s REST API. Actions cover creating and updating Bitlinks, expanding a short link back to its original destination, and listing an account’s Bitlinks by group, alongside summary and detailed click reporting for tracking how a link performs over time.
A list-groups action rounds out the set, since Bitly scopes link listing to one group at a time and every account needs at least its default group’s ID to use the others.
This is a focused slice of Bitly’s link and analytics surface: it does not manage custom domains, campaigns or bulk operations, keeping the footprint to the core loop of shortening, tracking and updating the links a workflow actually needs to touch.
Build with Bitly
Three routes to the same 8 actions. The Workflow tab is generated from Bitly'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.
Get Bitlink Clicks Summary
get-bitlink-clicks-summary Total click count for a Bitlink over a time window.
List Bitlinks
list-bitlinks List the Bitlinks in a group. Returns one page — pass `searchAfter` to walk.
Update Bitlink
update-bitlink Update title, archived state, tags, or the redirect target of a Bitlink.
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 Bitly's real ids.
{
"manifestVersion": "2",
"name": "bitly-example",
"steps": [
{
"id": "create-bitlink",
"uses": {
"app": "io.w6w.bitly",
"action": "create-bitlink",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"longUrl": "<longUrl>"
}
}
]
}Here are some of the things you can do
-
Create Bitlink
performcreate-bitlink -
Expand Bitlink
readexpand-bitlink -
Get Bitlink
readget-bitlink -
Get Bitlink Clicks
readget-bitlink-clicks -
Get Bitlink Clicks Summary
readget-bitlink-clicks-summary
+3 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 Bitly, 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 Bitly. 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: "create-bitlink",
payload: {
longUrl: "<value>",
// domain: "<value>",
// groupGuid: "<value>",
// title: "<value>",
// tags: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-bitlink --payload '{"longUrl":"<value>"}'Give an AI agent Bitly — without giving it Bitly'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.bitly#create-bitlink",
"input": {
"longUrl": "<longUrl>"
}
}
}
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 Bitly 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
Bitly'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. Bitly itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Bitly declares its own checks, so its health is a property of the app rather than something the host guesses at.
Bitly platform status
Reads status.bitly.com's Atom history feed for open (non-Resolved) incidents.