Marketo
Manage Marketo leads, static lists, companies and smart campaigns.
About
Marketo ships in the w6w first-party pack. It declares 15 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.marketo- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Customer Relationship Management
Overview
Marketo Engage is Adobe’s marketing automation platform, and this app puts the daily loop of running one — leads, static lists, companies and smart campaigns — behind a workflow, whichever pod your subscription happens to run on.
Lead management is the core of it: get a lead by ID, find leads by any field, create or update a lead by whatever key your instance dedupes on, delete leads, and describe the full field schema (standard and custom) before building a field map. List membership rounds it out with add, remove, list-members and is-member actions against a static list, and company create/update/find mirrors the lead sync shape for the account records leads roll up into.
Smart Campaigns get the two actions a workflow actually needs day to day: request a trigger campaign to push specific leads through its flow, and schedule a batch campaign to run — plus reading a campaign’s own metadata by ID or by browsing. Building or editing a campaign’s trigger/filter/flow graph itself stays out of scope, the same way this pack keeps Mautic’s campaign builder and Gitea’s admin surfaces out.
Deleting a lead is here as well, deliberately made harder to trigger by accident than everything else, gated behind an explicit confirmation the same way this pack gates every other irreversible delete.
Build with Marketo
Three routes to the same 15 actions. The Workflow tab is generated from Marketo'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 smart campaigns
campaign-list Browse smart campaigns, optionally filtered to only active trigger campaigns.
Schedule a batch campaign
campaign-schedule Schedule a batch smart campaign to run, optionally overriding its My Tokens.
Request a trigger campaign
campaign-trigger Pass one or more leads through a trigger campaign's flow.
Create or update a company
company-sync Create a company, update one, or either — deduped by externalCompanyId.
Create or update a lead
lead-sync Create a lead, update one, or either — Marketo dedupes by the lookup field.
Describe lead fields
leads-describe List every field available on the lead object, including custom fields.
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 Marketo's real ids.
{
"manifestVersion": "2",
"name": "marketo-example",
"steps": [
{
"id": "campaign-get",
"uses": {
"app": "io.w6w.marketo",
"action": "campaign-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"campaignId": "<campaignId>"
}
}
]
}Here are some of the things you can do
-
Get a smart campaign
readcampaign-get -
List smart campaigns
readcampaign-list -
Schedule a batch campaign
performcampaign-schedule -
Request a trigger campaign
performcampaign-trigger -
Find companies
searchcompany-get
+10 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 Marketo, 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 Marketo. 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: "campaign-get",
payload: {
campaignId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action campaign-get --payload '{"campaignId":"<value>"}'Give an AI agent Marketo — without giving it Marketo'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.marketo#campaign-get",
"input": {
"campaignId": "<campaignId>"
}
}
}
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 Marketo 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
Marketo'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. Marketo itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Marketo declares its own checks, so its health is a property of the app rather than something the host guesses at.
Marketo pod reachable
This connection's own pod, probed unsigned against /rest/v1/leads/describe.json. Marketo's documented 601/602 auth-error envelope proves the pod is up and answering — no credential is sent, so a rotated Client Secret must not make the pod look down.