BlueSnap ACTION
Update Vaulted Shopper
Update an existing vaulted shopper. The vaultedShopperId is returned by Create Vaulted Shopper or a transaction response; BlueSnap does not expose a list-all-shoppers endpoint. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's BlueSnap account once, then configure and run Update Vaulted Shopper 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: "bluesnap-update-vaulted-shopper",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
bluesnap: { authProvisionId: "apn_xxxxxxx" },
vaultedShopperId: "Vaulted Shopper ID",
firstName: "First 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": "bluesnap-update-vaulted-shopper",
"configured_props": {
"bluesnap": { "authProvisionId": "apn_xxxxxxx" },
"vaultedShopperId": "Vaulted Shopper ID",
"firstName": "First 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": "bluesnap",
},
},
},
)
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: "bluesnap-update-vaulted-shopper",
arguments: {
vaultedShopperId: "Vaulted Shopper ID",
firstName: "First 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 |
|---|---|---|
vaultedShopperId Vaulted Shopper ID | string | The numeric vaulted shopper ID to update (e.g. 20769005). Obtain it from the Create Vaulted Shopper response or a transaction record (BlueSnap has no list-shoppers endpoint). Required |
firstName First Name | string | Updated shopper first name. BlueSnap requires both name fields on update. Required |
lastName Last Name | string | Updated shopper last name. BlueSnap requires both name fields on update. Required |
email Email | string | Updated shopper email address. Optional |
country Country | string | Updated ISO 3166-1 alpha-2 country code (e.g. US, IN for India). Full country names such as India are rejected by BlueSnap. Optional |
city City | string | Updated shopper city. Optional |
state State | string | Updated shopper state/province. For US, Canada, and Brazil addresses BlueSnap requires the two-letter code (e.g. CA for California); other countries accept the full region name (e.g. Bavaria). Optional |
zip ZIP | string | Updated shopper ZIP/postal code, formatted for the shopper's country (e.g. 94107 for the US, M5H 2N2 for Canada). Optional |
phone Phone | string | Updated shopper phone number, digits with an optional leading + country code and separators (e.g. +1 415-555-0132). 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
- bluesnap-update-vaulted-shopper
- Version
- 0.0.1
- App
- BlueSnap
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗