Streak
Manage Streak CRM pipelines, boxes, stages, fields, contacts, organizations and tasks over the Streak API v1.
About
Streak ships in the w6w first-party pack. It declares 40 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.streak- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management
Overview
Streak is a CRM built directly on top of Gmail, and this app manages its pipelines, boxes (Streak’s term for a deal or record), stages, custom fields, contacts, organizations and tasks over the Streak API.
Pipelines, stages, fields, boxes and tasks each support the full list/get/create/update/delete lifecycle; contacts support the same create/get/update/delete lifecycle, found through the general search rather than a dedicated list call; organizations support only get, update and delete, since Streak derives an organization from its boxes and contacts rather than letting you create one directly. A general search reaches across boxes, contacts and organizations at once, and a separate name-scoped search covers boxes alone. Custom fields are modeled explicitly, since a Streak pipeline’s real data usually lives in fields the account defined itself rather than in the built-in ones.
Good for creating a Streak box and its contacts automatically from a form submission or another CRM, moving a deal along a pipeline as an external status changes, keeping contact and organization records in sync, and managing tasks tied to a box from an outside scheduling or reminder tool.
Build with Streak
Three routes to the same 40 actions. The Workflow tab is generated from Streak'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.
Delete Pipeline Field
field-delete Delete a custom field from a pipeline, along with its values on every box.
Update Pipeline Field
field-update Rename a pipeline field. A field's type cannot be changed once created.
Delete Pipeline
pipeline-delete Permanently delete a pipeline and every box in it. This cannot be undone.
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 Streak's real ids.
{
"manifestVersion": "2",
"name": "streak-example",
"steps": [
{
"id": "box-create",
"uses": {
"app": "io.w6w.streak",
"action": "box-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"pipelineKey": "<pipelineKey>",
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Create Box
performbox-create -
Get Box Field Value
readbox-field-value-get -
Update Box Field Value
performbox-field-value-update -
Get Box
readbox-get -
List Boxes
searchbox-list
+35 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 Streak, 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 Streak. 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: "box-create",
payload: {
pipelineKey: "<value>",
name: "<value>",
// stageKey: "<value>",
// notes: "<value>",
// assignedToEmails: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action box-create --payload '{"pipelineKey":"<value>","name":"<value>"}'Give an AI agent Streak — without giving it Streak'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.streak#box-create",
"input": {
"pipelineKey": "<pipelineKey>",
"name": "<name>"
}
}
}
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 Streak 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
Streak'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. Streak itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Streak declares its own checks, so its health is a property of the app rather than something the host guesses at.
Streak platform status
Component status from status.streak.com, keyed off the 'Streak API' component this app actually calls through — the other four components (streak.com, and the Gmail/Android/iOS clients) are reported as context, not folded into the verdict.
Rate limit headroom
Streak publishes no rate-limit or quota surface to probe.