Sendy ACTION
Add or Update a Subscriber
Adds a new subscriber or updates existing subscriber's details for a specific list. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Sendy account once, then configure and run Add or Update a Subscriber 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: "sendy-add-update-subscriber",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
sendy: { authProvisionId: "apn_xxxxxxx" },
brandId: "Brand ID",
list: "List ID",
},
})
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": "sendy-add-update-subscriber",
"configured_props": {
"sendy": { "authProvisionId": "apn_xxxxxxx" },
"brandId": "Brand ID",
"list": "List ID"
}
}'// 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": "sendy",
},
},
},
)
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: "sendy-add-update-subscriber",
arguments: {
brandId: "Brand ID",
list: "List ID",
},
})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 |
|---|---|---|
brandId Brand ID | string | The ID of the brand. Required Dynamic |
list List ID | string | The ID of the list you want to subscribe a user. Required Dynamic |
email Email | string | The email address of the subscriber. Required |
name Name | string | The user's name. Optional |
country Country | string | user's 2 letter country code. Optional |
ipaddress IP Address | string | The user's IP address. Optional |
referrer Referrer | string | The URL where the user signed up from. Optional |
gdpr GDPR | boolean | If you're signing up EU users in a GDPR compliant manner, set this to true. Optional |
silent silent | boolean | Set to True if your list is 'Double opt-in' but you want to bypass that and signup the user to the list as 'Single Opt-in instead' 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
- sendy-add-update-subscriber
- Version
- 0.0.2
- App
- Sendy
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗