First-party app
Outseta

Outseta

Manage Outseta people, accounts, deals, email lists, support cases, plans, subscriptions and invoices through the Outseta REST API.

stable Customer Relationship ManagementFinance & AccountingMarketing

About

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.

App id
io.w6w.outseta
Version
0.1.0
Author
w6w
Licence
MIT
Categories
Customer Relationship Management · Finance & Accounting · Marketing

Overview

Outseta 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.

Build with Outseta

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 Person to Account

add-account-member

Attach an existing person to an existing account, optionally sending them a welcome email.

Add Custom Activity

add-custom-activity

Record a custom event on an account, person or deal. The title can trigger drip-campaign automation.

Add Add-on Usage

add-usage

Record a usage entry against a usage-billed subscription add-on; it is billed at the end of the month.

Cancel Account

cancel-account

Record a cancellation request. The account must be Subscribing; it moves to Canceling and ends at renewal.

Create Account

create-account

Add a new account, optionally attaching an existing person as its primary contact.

Create Support Case

create-case

Open a support case from a person, optionally sending the automatic acknowledgement.

Create Deal

create-deal

Add a new deal to the CRM pipeline.

Create Person

create-person

Add a new person (a contact or user) to the account.

Delete Account

delete-account

Delete an account record. Irreversible.

Delete Deal

delete-deal

Delete a deal. Irreversible.

Delete Person

delete-person

Delete a person record. Irreversible.

Get Account

get-account

Retrieve one account by Uid. Use `fields` to include the current subscription and plan.

Get Support Case

get-case

Retrieve one support case with its history.

Get Deal

get-deal

Retrieve one deal by Uid.

Get Email List

get-email-list

Retrieve one email list by Uid.

Get Invoice

get-invoice

Retrieve one invoice by Uid.

Get Person

get-person

Retrieve one person by Uid, including their account memberships.

Get Plan

get-plan

Retrieve one plan by Uid.

Get Subscription

get-subscription

Retrieve one subscription by Uid.

List Accounts

list-accounts

List accounts (the customers being billed), optionally by name search, segment or billing stage.

List Activities

list-activities

List the activity feed, optionally for one entity. Limited to the last year unless a date filter is given.

List Knowledge Base Articles

list-articles

List knowledge base articles, optionally matching title or body text.

List Support Cases

list-cases

List support cases, optionally by search string or tag.

List Deals

list-deals

List CRM deals, optionally by owner or a name/stage/account search.

List Email Lists

list-email-lists

List the account's email lists with their subscriber counts.

List Email List Subscribers

list-email-subscribers

List the subscribers of an email list, optionally matching a name or email.

List Invoices

list-invoices

List invoices, optionally omitting one by Uid.

List People

list-people

List the people in the account one page at a time, optionally matching a name or email.

List Plan Families

list-plan-families

List plan families (the groupings plans belong to).

List Plans

list-plans

List the subscription plans, with pricing when `fields` expands them.

List Subscriptions

list-subscriptions

List subscriptions across accounts, optionally only current, future or past ones.

List Account Transactions

list-transactions

List the invoice, payment, credit, refund and chargeback transactions of one account.

Remove Account Cancellation

remove-account-cancellation

Withdraw a previous cancellation request so the account keeps subscribing.

Remove Person from Account

remove-account-member

Remove a membership from an account. The person record is kept.

Subscribe to Email List

subscribe-to-email-list

Subscribe a person to a list — an existing one by Uid, or a new one by email address.

Remove Email List Subscriber

unsubscribe-from-email-list

Remove a subscription from an email list.

Update Account

update-account

Update properties on an account. Billing stage is not editable — it follows subscription activity.

Update Deal

update-deal

Update properties on a deal. Only the properties you send change.

Update Person

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>"
      }
    }
  ]
}

Here are some of the things you can do

  • Add Person to Account

    perform
    add-account-member
  • Add Custom Activity

    perform
    add-custom-activity
  • Add Add-on Usage

    perform
    add-usage
  • Create Account

    perform
    create-account
  • Create Support Case

    perform
    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.

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: "add-account-member",
  payload: {
    accountUid: "<value>",
    personUid: "<value>",
    // isPrimary: "<value>",
    // receiveInvoices: "<value>",
    // sendWelcomeEmail: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);
Install the CLI
npm install -g @w6w/cli
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.

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

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).

Request MCP access

Health checks

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

service

Outseta platform status

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.

quota

API rate-limit headroom