Zoho CRM ACTION
Upsert Records
Inserts new records or updates existing ones based on duplicate check field values. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Zoho CRM account once, then configure and run Upsert Records 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: "zoho_crm-upsert-records",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zoho_crm: { authProvisionId: "apn_xxxxxxx" },
module: "Module",
data: "Data",
},
})
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": "zoho_crm-upsert-records",
"configured_props": {
"zoho_crm": { "authProvisionId": "apn_xxxxxxx" },
"module": "Module",
"data": "Data"
}
}'// 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": "zoho_crm",
},
},
},
)
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: "zoho_crm-upsert-records",
arguments: {
module: "Module",
data: "Data",
},
})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 |
|---|---|---|
module Module | string | Module where the record will be created. Use the List Modules action to get the list of available modules. Required Dynamic |
data Data | string | An array of record objects to insert or update (maximum 100). Use Field API names as keys (e.g., Last_Name, Email). Each record may include $append_values for multi-select picklists. Use the List Fields action to get available field API names. Required |
duplicateCheckFields Duplicate Check Fields | string[] | Field API names to use for duplicate checking (e.g., Email, Phone). If not specified, system-defined duplicate check fields are used first, followed by user-defined unique fields. Optional |
skipCadences Skip Cadences | boolean | Whether to skip Cadences execution during record upsert. Optional |
skipCadencesAction Skip Cadences Action | string | The action for which to skip Cadences execution. Required when Skip Cadences is enabled. Optional |
trigger Trigger | string[] | Workflow triggers to execute. Use an empty array [] to skip all workflows, approvals, and blueprints. Optional |
applyFeatureExecution Apply Feature Execution | string[] | Additional CRM checks to trigger during record creation or update. Optional |
ifUnmodifiedSince If Unmodified Since | string | ISO 8601 timestamp (e.g., 2024-01-15T15:26:49+05:30). The upsert will fail if the record was modified after this time. 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
- zoho_crm-upsert-records
- Version
- 0.0.3
- App
- Zoho CRM
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗