Manage Outseta people, accounts, deals, email lists, support cases, plans, subscriptions and invoices through the Outseta REST API.
Outseta ships in the w6w first-party pack. It declares 39 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
io.w6w.outsetaOutseta is an all-in-one back office for SaaS products: user accounts and sign-up, subscription billing, a CRM, email marketing and a support desk, sold as one platform. This app lets a workflow read and change that data without a second integration.
On the CRM side it can list, look up, create, update and delete people, accounts and deals, attach people to accounts and record or withdraw a cancellation request. For marketing it lists email lists and their subscribers and subscribes or removes people. Support cases can be listed, read and opened, and the knowledge base can be searched.
For billing it reads plans, plan families, subscriptions, invoices and an account’s transactions, and records metered usage against a usage-billed add-on. Activity feeds can be read, and custom events written, so a workflow can drive Outseta’s drip campaigns.
Every Outseta account lives on its own subdomain, so a connection takes the subdomain plus an API key and secret from Settings > Integrations > API Keys. List actions share Outseta’s paging, field-selection, ordering and property-filter options.
Three routes to the same 39 actions. The Workflow tab is generated from Outseta'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.
add-account-member Attach an existing person to an existing account, optionally sending them a welcome email.
add-custom-activity Record a custom event on an account, person or deal. The title can trigger drip-campaign automation.
add-usage Record a usage entry against a usage-billed subscription add-on; it is billed at the end of the month.
cancel-account Record a cancellation request. The account must be Subscribing; it moves to Canceling and ends at renewal.
create-account Add a new account, optionally attaching an existing person as its primary contact.
create-case Open a support case from a person, optionally sending the automatic acknowledgement.
get-account Retrieve one account by Uid. Use `fields` to include the current subscription and plan.
list-accounts List accounts (the customers being billed), optionally by name search, segment or billing stage.
list-activities List the activity feed, optionally for one entity. Limited to the last year unless a date filter is given.
list-articles List knowledge base articles, optionally matching title or body text.
list-email-subscribers List the subscribers of an email list, optionally matching a name or email.
list-people List the people in the account one page at a time, optionally matching a name or email.
list-subscriptions List subscriptions across accounts, optionally only current, future or past ones.
list-transactions List the invoice, payment, credit, refund and chargeback transactions of one account.
remove-account-cancellation Withdraw a previous cancellation request so the account keeps subscribing.
remove-account-member Remove a membership from an account. The person record is kept.
subscribe-to-email-list Subscribe a person to a list — an existing one by Uid, or a new one by email address.
update-account Update properties on an account. Billing stage is not editable — it follows subscription activity.
update-person Update one or more properties on a person. Only the properties you send change.
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 Outseta's real ids.
{
"manifestVersion": "2",
"name": "outseta-example",
"steps": [
{
"id": "add-account-member",
"uses": {
"app": "io.w6w.outseta",
"action": "add-account-member",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"accountUid": "<accountUid>",
"personUid": "<personUid>"
}
}
]
}add-account-member add-custom-activity add-usage create-account create-case +34 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 Outseta, 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 Outseta. 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: "add-account-member",
payload: {
accountUid: "<value>",
personUid: "<value>",
// isPrimary: "<value>",
// receiveInvoices: "<value>",
// sendWelcomeEmail: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value); npm install -g @w6w/cli w6w run conn_YOUR_CONNECTION_ID --action add-account-member --payload '{"accountUid":"<value>","personUid":"<value>"}' Give an AI agent Outseta — without giving it Outseta'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.outseta#add-account-member",
"input": {
"accountUid": "<accountUid>",
"personUid": "<personUid>"
}
}
}
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 Outseta connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
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.
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.
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.
Outseta'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. Outseta itself is MIT, and the runtime that executes it is source-available (FSL).
Outseta declares its own checks, so its health is a property of the app rather than something the host guesses at.
Reads status.outseta.com's Oh Dear-powered RSS feed for open incidents. The feed has carried no items, so the open/resolved title convention is a best reading rather than a confirmed one.