Log in Sign up
First-party app
Segment

Segment

Send identify, track, page, group, alias and batch calls to Segment's Tracking API.

stable Analytics & BI

About

Segment ships in the w6w first-party pack. It declares 6 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.

App id
io.w6w.segment
Version
0.1.2
Author
w6w
Licence
MIT
Categories
Analytics & BI

Overview

Segment’s Tracking API is the write side of a customer-data pipeline, and this app implements its full verb set: identify a person by their traits, track a named event, record a page view, associate a user with a group or account, alias two identities together as one, and batch up to 2,500 of any of those calls into a single request. Free-form trait, property and context objects pass straight through to Segment untouched, so the wire shape a workflow builds is exactly what Segment receives.

Segment splits its API in two — a write-only Tracking API for events and a separate config API for managing sources and warehouses — and this app deliberately calls only the Tracking API, so it has nothing to say about workspace configuration. Every call is idempotent: a message id derived from the invocation is attached to each event, so a host’s retry of the same run lands on Segment’s own deduplication window rather than double-recording it.

Build with Segment

Three routes to the same 6 actions. The Workflow tab is generated from Segment'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.

Alias

alias

Merge a previous identity (often an Anonymous ID) into a user's new identity.

Batch

batch

Send up to 2,500 identify/track/page/group/alias calls in one request.

Group

group

Associate a user with a group — a company, team, or account.

Identify

identify

Tie a user to their traits (name, email, plan, …).

Track Page

page

Record a page view.

Track Event

track

Record an action a user performed.

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 Segment's real ids. 

{
  "manifestVersion": "2",
  "name": "segment-example",
  "steps": [
    {
      "id": "alias",
      "uses": {
        "app": "io.w6w.segment",
        "action": "alias",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "userId": "<userId>"
      }
    }
  ]
}

Here are some of the things you can do

  • Alias

    perform
    alias

  • Batch

    perform
    batch

  • Group

    perform
    group

  • Identify

    perform
    identify

  • Track Page

    perform
    page

+1 more action 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 Segment, 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 Segment. The Workflow tab is where this app's real ids are.

Install 
npm install @w6w/sdk
yarn add @w6w/sdk
pnpm add @w6w/sdk
deno add npm:@w6w/sdk
Code 
import { 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: "track",
  payload: {
    event: "<value>",
    // userId: "<value>",
    // anonymousId: "<value>",
    // properties: "<value>",
    // context: "<value>",
    // integrations: "<value>",
    // timestamp: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);
Install the CLI 
npm install -g @w6w/cli
CLI 
w6w run conn_YOUR_CONNECTION_ID --action track --payload '{"event":"<value>"}'

Give an AI agent Segment — without giving it Segment'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.segment#alias",
    "input": {
      "userId": "<userId>"
    }
  }
}

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 Segment 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

Segment'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. Segment itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

Segment declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

Segment platform status

Atlassian Statuspage rollup for status.segment.com, with per-component detail. Unauthenticated and unsigned.

quota

API quota