Rydoo ACTION
Update User Profile
Modifies existing user details like names, nationality, or status. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Rydoo account once, then configure and run Update User Profile 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: "rydoo-update-user-profile",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
rydoo: { authProvisionId: "apn_xxxxxxx" },
userId: "User",
email: "Email",
},
})
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": "rydoo-update-user-profile",
"configured_props": {
"rydoo": { "authProvisionId": "apn_xxxxxxx" },
"userId": "User",
"email": "Email"
}
}'// 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": "rydoo",
},
},
},
)
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: "rydoo-update-user-profile",
arguments: {
userId: "User",
email: "Email",
},
})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 |
|---|---|---|
userId User | string | The user to whom the expense belongs (e.g., d290f1ee-6c54-4b01-90e6-d701748f0851) Required Dynamic |
email Email | string | New email address. Must be unique within the company account Optional |
firstName First Name | string | New first name of the user Optional |
lastName Last Name | string | New last name of the user Optional |
enabled Enabled | boolean | When true, activates the account and sends a verification email Optional |
refId Reference ID | string | External reference identifier, often used for employee or vendor numbers in ERP systems Optional |
authentication Authentication | string | Authentication type for the user. Defaults to company settings if unspecified Optional |
country Country | string | 3-letter country code per ISO 3166 (e.g., FRA, DEU, USA) Optional |
languageCountryCode Language | string | User interface language as a BCP 47 locale tag in language-region format (e.g., en-US, de-DE) Optional |
accountNumber Account Number | string | Direct deposit account number for expense reimbursements Optional |
customFields Custom Fields | string[] | Custom field values for the user. Each entry must be a JSON object with key, value, and optionally valueCode properties (e.g., {"key": "department", "value": "Engineering"}) 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
- rydoo-update-user-profile
- Version
- 0.0.2
- App
- Rydoo
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗