Unbounce
Manage Unbounce landing pages, leads and form submissions, and read account, sub-account and domain structure.
About
Unbounce ships in the w6w first-party pack. It declares 24 actions, 1 health check, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.unbounce- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Forms & Surveys · Analytics & BI
Overview
Unbounce builds and hosts landing pages, pop-ups and sticky bars for conversion campaigns. This app covers the full read path of the Unbounce REST API (v0.4): the account hierarchy (accounts, sub-accounts/clients, custom domains, page groups), a page’s own metadata and A/B test stats, and the leads a page’s forms have collected — plus creating a lead programmatically (for a workflow that captures a submission somewhere else and needs it to show up in Unbounce) and requesting asynchronous deletion of one or more leads for privacy/compliance workflows.
Unbounce’s account model has three levels most integrations get wrong on the first try: an Account owns Sub-Accounts (Unbounce calls these “Clients”), and Sub-Accounts own Domains, Page Groups and Pages — so “list every page” depends on which level a Connection’s credential can see, and this app exposes each level’s own page list separately rather than assuming one global list is enough.
Health checks track Unbounce’s own status page, weighted toward its own “Partner API” component rather than the page-level indicator, so a marketing-site incident doesn’t report the API as down.
Build with Unbounce
Three routes to the same 24 actions. The Workflow tab is generated from Unbounce'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 Pages by Account
account-page-list Retrieve all pages for the given account, across every sub-account.
List Sub-Accounts
account-sub-account-list Retrieve all sub-accounts (called "Clients" in the Unbounce app) for the given account.
Get API Info
api-meta-get Retrieve the global API meta-information: documentation link and entry points.
Get Lead
lead-get Retrieve a single lead by its own id, without needing to know which page it came from.
List Form Fields
page-form-field-list Retrieve every form field across all variants of a page (name, type, validations).
Create Lead
page-lead-create Record a form submission for a page as a new lead, as if a visitor had submitted it.
Delete Lead
page-lead-delete Permanently delete a single lead. Deleted leads cannot be recovered. Requires an OAuth connection and account-owner permissions — an API Key connection is refused here.
Request Lead Deletion
page-lead-deletion-request-create Create an asynchronous request to delete one or more leads for a page. Requires an OAuth connection and account-owner permissions — an API Key connection is refused here. Deleted leads cannot be recovered.
Get Lead Deletion Request
page-lead-deletion-request-get Retrieve the status of an in-progress or completed asynchronous lead deletion.
List Leads
page-lead-list Retrieve all leads (form submissions) for a given page, pop-up, sticky bar, or AMP page.
List Pages
page-list Retrieve all pages for the authenticated principal (API key or OAuth client), including pages owned by a different sub-account this principal was invited onto.
List Domains
sub-account-domain-list Retrieve all custom domains registered under a given sub-account.
Get Sub-Account
sub-account-get Retrieve the details of a single sub-account (called a "Client" in the Unbounce app).
List Page Groups
sub-account-page-group-list Retrieve all page groups for a given sub-account. Pages may optionally be organized into groups.
Get Current User
user-get-self Retrieve the user this connection authenticates as, and the accounts they can see.
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 Unbounce's real ids.
{
"manifestVersion": "2",
"name": "unbounce-example",
"steps": [
{
"id": "account-get",
"uses": {
"app": "io.w6w.unbounce",
"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 Pages by Account
searchaccount-page-list -
List Sub-Accounts
searchaccount-sub-account-list -
Get API Info
readapi-meta-get
+19 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 Unbounce, 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 Unbounce. 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 Unbounce — without giving it Unbounce'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.unbounce#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 Unbounce 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
Unbounce'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. Unbounce itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Unbounce declares its own checks, so its health is a property of the app rather than something the host guesses at.
Unbounce Partner API status
The status.unbounce.com "Partner API" component's own state — not the page-level indicator, which also covers the marketing site, live support channels and two dozen AWS infrastructure rows that say nothing about api.unbounce.com.