Simplero
Manage Simplero contacts, tags, lists, automations, courses, products, purchases and sites through the Simplero API v2.
About
Simplero ships in the w6w first-party pack. It declares 35 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.simplero- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Customer Relationship Management · Commerce & Payments
Overview
Simplero is an all-in-one platform for coaches, course creators and membership businesses: email lists and broadcasts, automations, products and payments, courses and member sites. This app lets a workflow work with the contact and commerce side of a Simplero account through the Simplero API v2.
Create, update and look up contacts, tag and untag them, subscribe them to or remove them from an email list, start or stop an automation for them, grant or revoke access to a course or a member site, and record a product purchase or cancellation without taking payment. Read-side actions list and fetch tags, email lists, products, purchases, list subscriptions, courses, access grants, sites, broadcasts and automations, with Simplero’s own page, per-page and cursor pagination.
Simplero’s API calls people “customers” in its paths but “contacts” everywhere in its interface; this app uses “contact”. The v2 API has no delete endpoint for contacts and no webhook-management endpoints, so neither is offered here.
Build with Simplero
Three routes to the same 35 actions. The Workflow tab is generated from Simplero'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.
List Access Grants
access-grant-list List access grants — which contact has been given access to which course, site or other resource, with the start and end of that access.
List Automations
automation-list List the account's automations. Automations that run on contacts have object type `Customer`; those are the ones Start Automation / Stop Automation can target.
Get Broadcast
broadcast-get Fetch one email broadcast by its numeric id, including its delivery and engagement counts.
List Broadcasts
broadcast-list List email broadcasts (read-only), optionally by delivery state or recipient list. Each record carries its sent, open, click, bounce and unsubscribe counts.
Start Automation for Contact
contact-automation-start Start an automation for a contact. The automation must run on contacts (object type `Customer`).
Stop Automation for Contact
contact-automation-stop Stop an automation that is running for a contact.
Create Contact
contact-create Create a contact (Simplero's `customers` resource). Creating a contact does not subscribe it to any list or tag it — follow with Subscribe to List or Add Tag.
List Contacts
contact-list List the account's contacts (Simplero's `customers` resource), optionally filtered by exact email, tag or lead/customer status. Without a filter this pages the whole contact base, 20 at a time by default.
Subscribe Contact to List
contact-list-subscribe Subscribe a contact to an email list. By default Simplero sends the list's welcome email and starts its auto-responses; the switches below suppress that.
Record Product Purchase
contact-product-purchase Give a contact a product as if purchased, WITHOUT taking payment (Simplero: 'Purchase product without paying'). Use it to grant a product that was paid for elsewhere.
Grant Site Access
contact-site-grant Give a contact access to a member site, optionally emailing them a login link.
Update Contact
contact-update Update a contact's profile fields. Only the fields you set are sent, so the others are left as they are.
List Purchases
purchase-list List purchases (orders), optionally for one contact and/or one product. Amounts are in cents (`received_price_cents`, `received_total_cents`) alongside a `currency_code`.
List List Subscriptions
subscription-list List email-list subscriptions (which contact is on which list, and whether it is active or unsubscribed), optionally for one list or one tag.
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 Simplero's real ids.
{
"manifestVersion": "2",
"name": "simplero-example",
"steps": [
{
"id": "automation-get",
"uses": {
"app": "io.w6w.simplero",
"action": "automation-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Automation
readautomation-get -
List Access Grants
readaccess-grant-list -
List Automations
readautomation-list -
Get Broadcast
readbroadcast-get -
List Broadcasts
readbroadcast-list
+30 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 Simplero, 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 Simplero. 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: "automation-get",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action automation-get --payload '{"id":"<value>"}'Give an AI agent Simplero — without giving it Simplero'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.simplero#automation-get",
"input": {
"id": "<id>"
}
}
}
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 Simplero 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
Simplero'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. Simplero itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Simplero declares its own checks, so its health is a property of the app rather than something the host guesses at.
Simplero platform status
Component status from status.simplero.com. The `API` component decides the verdict. Background processing, the website and the third parties Simplero depends on (AWS, Spreedly, Stripe, Twilio) are reported per component but can only lower the verdict to degraded, since an outage there does not stop API calls.
Request-rate headroom
Not exposed: Simplero's v2 OpenAPI document declares no 429 response and no rate-limit header, the API description states no request limit, and a 401 answer carries no rate-limit header.