AWeber
Manage AWeber email lists, subscribers and broadcasts — add and update subscribers, read and schedule broadcast newsletters, and manage tags and custom fields.
About
AWeber ships in the w6w first-party pack. It declares 33 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.aweber- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Email · Marketing
Overview
AWeber is an email marketing and newsletter platform built around Lists, Subscribers and Broadcasts. This app covers the API’s full v1 surface for those three resources: reading and finding lists, adding, finding, updating, moving and removing subscribers (by ID or by email), tracking e-commerce purchases against a subscriber, and creating, updating, scheduling, cancelling and reading the open/click stats of broadcast newsletters. It also covers list-scoped Tags, Custom Fields and Segments, and the account-level resources every call is scoped under.
Authorization is OAuth 2.0 (AWeber’s older OAuth 1.0a is still accepted by the API but is not implemented here — see the README). Health checks track AWeber’s own status page alongside the credential’s own liveness.
Build with AWeber
Three routes to the same 33 actions. The Workflow tab is generated from AWeber'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.
Create Broadcast
broadcast-create Create a draft broadcast newsletter. Provide body_html and/or body_text.
List Broadcasts
broadcast-list List a list's broadcasts by status. Draft only returns drafts created through this API.
Update Broadcast
broadcast-update Replace a draft broadcast's subject or body. API-created drafts only.
Update Custom Field
custom-field-update Rename a custom field, or change whether a subscriber may update it.
Record Purchase
purchase-create Record a purchase (or any tracked value event) against a subscriber, creating or updating them in the process.
Add Subscriber
subscriber-add Add a subscriber to a list. Not for bulk loads — use AWeber's list importer.
Delete Subscriber
subscriber-delete Permanently delete a subscriber and their activity history. To just unsubscribe them (keeping history), use Update Subscriber with status unsubscribed instead.
Delete Subscriber by Email
subscriber-delete-by-email Permanently delete a subscriber and their activity history, addressed by email.
Find Subscribers
subscriber-find Search subscribers on one list by email, status, tags, or subscribe date.
Find Subscribers Across Lists
subscriber-find-across-lists Search subscribers on every list of an account at once.
Move Subscriber
subscriber-move Move a subscriber from one list to another list on the same account.
Update Subscriber by Email
subscriber-update-by-email Update a subscriber's fields, status, or tags, addressed by email.
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 AWeber's real ids.
{
"manifestVersion": "2",
"name": "aweber-example",
"steps": [
{
"id": "account-get",
"uses": {
"app": "io.w6w.aweber",
"action": "account-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"accountId": "<accountId>"
}
}
]
}Here are some of the things you can do
-
Get Account
readaccount-get -
List Accounts
searchaccount-list -
List Broadcast Clicks
searchbroadcast-clicks -
Create Broadcast
performbroadcast-create -
Get Broadcast
readbroadcast-get
+28 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 AWeber, 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 AWeber. 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: "account-get",
payload: {
accountId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action account-get --payload '{"accountId":"<value>"}'Give an AI agent AWeber — without giving it AWeber'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.aweber#account-get",
"input": {
"accountId": "<accountId>"
}
}
}
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 AWeber 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
AWeber'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. AWeber itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
AWeber declares its own checks, so its health is a property of the app rather than something the host guesses at.
AWeber platform status
Component status from status.aweber.com. Covers the main site, customer logins, email sending, the API, subscriber sign-ups, sign-up form hosting, image hosting, newsletter archives, customer solutions and landing pages.
Request-rate headroom
Not exposed: AWeber documents its 120 requests/minute limit only in prose and returns no rate-limit headers on any response.