Mailchimp ACTION
Edit A Campaign Template Content
Edits a defined content area of a custom HTML template. See docs here
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Mailchimp account once, then configure and run Edit A Campaign Template Content from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "mailchimp-edit-campaign-template-content",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
mailchimp: { authProvisionId: "apn_xxxxxxx" },
campaignId: "Campaign ID",
archiveType: "Archive type",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "mailchimp-edit-campaign-template-content",
"configured_props": {
"mailchimp": { "authProvisionId": "apn_xxxxxxx" },
"campaignId": "Campaign ID",
"archiveType": "Archive type"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "mailchimp",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "mailchimp-edit-campaign-template-content",
arguments: {
campaignId: "Campaign ID",
archiveType: "Archive type",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
campaignId Campaign ID | string | The unique ID of the campaign Required Dynamic |
archiveType Archive type | string | The type of encoded file. Optional |
templateSections Template sections | object | Content for the sections of the template. Each key should be the unique mc:edit area name from the template. Optional |
plainText Plain text | string | The plain-text portion of the campaign. If left unspecified, we'll generate this automatically. Optional |
html Plain text | string | The plain-text portion of the campaign. If left unspecified, we'll generate this automatically. Optional |
url URL | string | When importing a campaign, the URL where the HTML lives. Optional |
variateContents Variate contents | string[] | Stringified object list of content options for Multivariate Campaigns.
Allowed keys are archive, template, content_label, plain_text, html, and url.
Each content option must provide HTML content and may optionally provide plain text.
For campaigns not testing content, only one object should be provided. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- mailchimp-edit-campaign-template-content
- Version
- 0.0.3
- App
- Mailchimp
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗