Vero
Identify, track, tag, alias, delete, and subscribe/unsubscribe users via Vero's Track API.
About
Vero ships in the w6w first-party pack. It declares 7 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.vero- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Email · Marketing
Overview
Vero’s Track API is the write side of customer data for its customer-engagement platform — creating and updating user profiles, recording events, editing tags, changing (aliasing) a user’s identifier, deleting a user outright, and globally subscribing or unsubscribing a user from email. This app implements exactly that surface, the seven verbs that have been stable and unchanged since before 2016.
Vero exposes a second, separate REST surface — the Campaigns API — for managing broadcasts, journeys and preference-center topics. This app deliberately does not call it: it is a public preview that Vero grants access to only on request (a distinct API key most connections will not have), and its resource schemas (Broadcast, Journey, Topic, and their nested Message/Content children) are a different, much larger surface than the stable Track API this app targets. Noted here rather than silently dropped.
A few operations carry consequences worth knowing: deleting a user is permanent and not recoverable, aliasing (reidentifying) a user retargets their id so a retry against the old id no longer resolves, and Vero automatically deduplicates identical Track Event calls (same auth token, event name, identity and data) within a five-minute window, so a host retry converges on the original event rather than double-firing it.
Build with Vero
Three routes to the same 7 actions. The Workflow tab is generated from Vero'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.
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 Vero's real ids.
{
"manifestVersion": "2",
"name": "vero-example",
"steps": [
{
"id": "alias",
"uses": {
"app": "io.w6w.vero",
"action": "alias",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>",
"newId": "<newId>"
}
}
]
}Here are some of the things you can do
-
Alias User
performalias -
Add/Remove Tags
performedit-tags -
Identify User
performidentify -
Resubscribe User
performresubscribe -
Track Event
performtrack
+2 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 Vero, 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 Vero. 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: "alias",
payload: {
id: "<value>",
newId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action alias --payload '{"id":"<value>","newId":"<value>"}'Give an AI agent Vero — without giving it Vero'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.vero#alias",
"input": {
"id": "<id>",
"newId": "<newId>"
}
}
}
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 Vero 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
Vero'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. Vero itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Vero declares its own checks, so its health is a property of the app rather than something the host guesses at.
Vero platform status
Atlassian Statuspage rollup for status.getvero.com, with per-component detail. Unauthenticated and unsigned.