Customer Fields ACTION
Update Customer
Update an existing customer's information with new provided data. See the documentation.
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Customer Fields account once, then configure and run Update Customer 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: "customer_fields-update-customer",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
customer_fields: { authProvisionId: "apn_xxxxxxx" },
formId: "Form ID",
customerId: "Customer 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": "customer_fields-update-customer",
"configured_props": {
"customer_fields": { "authProvisionId": "apn_xxxxxxx" },
"formId": "Form ID",
"customerId": "Customer 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": "customer_fields",
},
},
},
)
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: "customer_fields-update-customer",
arguments: {
formId: "Form ID",
customerId: "Customer 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 |
|---|---|---|
formId Form ID | string | The form ID that will be attached to the customer. Note that any settings will be applied to the customer from the form. For example, if the form requires account approval, the customer will be submitted as a pending status. Optional Dynamic |
customerId Customer ID | string | The ID of the customer to update. Required Dynamic |
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
- customer_fields-update-customer
- Version
- 0.0.2
- App
- Customer Fields
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗