AcyMailing ACTION
Add or Update User
Creates a new user or updates an existing user in AcyMailing. If the user exists, will update the user's data with provided information. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's AcyMailing account once, then configure and run Add or Update User 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: "acymailing-add-update-user",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
acymailing: { authProvisionId: "apn_xxxxxxx" },
email: "Email",
name: "Name",
},
})
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": "acymailing-add-update-user",
"configured_props": {
"acymailing": { "authProvisionId": "apn_xxxxxxx" },
"email": "Email",
"name": "Name"
}
}'// 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": "acymailing",
},
},
},
)
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: "acymailing-add-update-user",
arguments: {
email: "Email",
name: "Name",
},
})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 |
|---|---|---|
email Email | string | The email address is used when updating an existing user. Required |
name Name | string | Any character should be available. Optional |
active Active | boolean | Defaults to true. Optional |
confirmed Confirmed | boolean | The confirmation is related to the "Require confirmation" option in the configuration, tab "Subscription". Optional |
cmsId CMS Id | integer | The cms_id must match the ID of the corresponding Joomla/WordPress user. Optional |
customFields Custom Fields | object | An object of field Ids and values. Optional |
triggers Triggers | boolean | Defaults to true. Defines if the saving of the user triggers automated tasks like follow-up campaigns and automations. Optional |
sendConf Send Conf | boolean | Defaults to true. Defines if the confirmation email should be sent when a new user is created. 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
- acymailing-add-update-user
- Version
- 0.0.3
- App
- AcyMailing
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗