Little Green Light
Search, read and log constituents, gifts, notes, appeals, campaigns, funds and groups in Little Green Light, the nonprofit CRM.
About
Little Green Light ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.littlegreenlight- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Finance & Accounting
Overview
Little Green Light (LGL) is a web-based CRM built for small and mid-size nonprofits to track constituents (donors, volunteers, members), gifts, notes, appeals, campaigns, funds and groups. This app covers LGL’s documented REST API v1: searching and reading constituents, listing and logging gifts and notes against a constituent record, and reading appeals, campaigns, funds and groups.
Every path, parameter and model in this app was verified on 2026-09-05 against LGL’s own machine-readable API reference — the Swagger 1.2 JSON served at https://api.littlegreenlight.com/api-docs/json/api-docs.json plus its 33 per-resource sub-documents — and against live probes of api.littlegreenlight.com.
Three things worth knowing before scripting against this API directly:
- Authentication is a plain Bearer token, not the HTTP Basic the server’s own
WWW-Authenticateheader implies for a request with noAuthorizationheader at all. A garbage or expired token gets a second, more specific challenge instead —WWW-Authenticate: Bearer realm="Rack::OAuth2 Protected Resources"with a structured{"error":"invalid_token",...}JSON body — which is the one this app’stesthook actually classifies on. - Search filters are an array of embedded
key=valuestrings (q[]=name=brady, repeatable for multiple constraints), not a single free-text query parameter — copying a plain search term intoqsilently returns nothing. - Every list response shares one envelope —
{ api_version, items_count, total_items, limit, offset, next_item, next_link, item_type, items: [...] }— across every one of the 33 documented resources, so pagination is uniform even though there is no separate ‘pagination’ section in the reference.
See README.md for the full per-action detail, what was verified against the spec, and what was deliberately left out.
Build with Little Green Light
Three routes to the same 12 actions. The Workflow tab is generated from Little Green Light'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.
Search Constituents
constituent-search Search active constituents. Confirmed filter field: 'name' (e.g. "name=brady"). Confirmed sort fields: name, external_id, lgl_id, date_created, date_updated, membership_level, membership_end_date_from.
Search Gifts
gift-search Search gifts across every constituent. Confirmed filter field: 'updated_from' (e.g. "updated_from=2016-01-01"). Confirmed sort fields: name, gift_amount, date, date_created, date_updated, fund, appeal, campaign, gift_type.
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 Little Green Light's real ids.
{
"manifestVersion": "2",
"name": "littlegreenlight-example",
"steps": [
{
"id": "constituent-create",
"uses": {
"app": "io.w6w.littlegreenlight",
"action": "constituent-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"first_name": "<first_name>",
"last_name": "<last_name>"
}
}
]
}Here are some of the things you can do
-
Create Constituent
performconstituent-create -
List Appeals
readappeal-list -
List Campaigns
readcampaign-list -
Get Constituent
readconstituent-get -
Search Constituents
searchconstituent-search
+7 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 Little Green Light, 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 Little Green Light. 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: "constituent-create",
payload: {
first_name: "<value>",
last_name: "<value>",
// is_org: "<value>",
// org_name: "<value>",
// email: "<value>",
// external_constituent_id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action constituent-create --payload '{"first_name":"<value>","last_name":"<value>"}'Give an AI agent Little Green Light — without giving it Little Green Light'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.littlegreenlight#constituent-create",
"input": {
"first_name": "<first_name>",
"last_name": "<last_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 Little Green Light 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
Little Green Light'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. Little Green Light itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Little Green Light declares its own checks, so its health is a property of the app rather than something the host guesses at.
Little Green Light platform status
No machine-readable status surface: status.littlegreenlight.com and littlegreenlight.statuspage.io both redirect to Statuspage's own unclaimed-page destination, and no other status feed for this vendor was found.
API quota headroom
Not exposed: no rate-limit/quota header appears on any live response (including a 401), and none of LGL's documented resources exposes a usage/limits endpoint.