Notion ACTION
Update Data Source
Update a Notion database (data source): rename it, change its description, or add/rename/retype its columns. Provide the data source ID (use Search with
filter: data_source to resolve a database name, or Retrieve Database Schema to inspect existing columns). properties is a JSON object of changes: to add a column, use a new name → type (e.g. { "Location": "rich_text" }); to rename/retype an existing column, key it by its current name/ID. Each value is a property schema object or a shorthand type name. See the documentation- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Notion account once, then configure and run Update Data Source 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: "notion-update-database",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
notion: { authProvisionId: "apn_xxxxxxx" },
dataSourceId: "Data Source ID",
title: "Title",
},
})
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": "notion-update-database",
"configured_props": {
"notion": { "authProvisionId": "apn_xxxxxxx" },
"dataSourceId": "Data Source ID",
"title": "Title"
}
}'// 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": "notion",
},
},
},
)
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: "notion-update-database",
arguments: {
dataSourceId: "Data Source ID",
title: "Title",
},
})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 |
|---|---|---|
dataSourceId Data Source ID | string | The ID of the database's data source. Use Search ( filter: data_source) or Retrieve Database Schema to find it. Required |
title Title | string | A new title for the data source. If omitted, the title is unchanged. Optional |
description Description | string | A new description for the data source. If omitted, the description is unchanged. Optional |
properties Properties | string | JSON object of column changes. To add a column: { "Location": "rich_text" }. To rename/retype: key by the current column name. Example: { "Priority": { "select": { "options": [ { "name": "High" } ] } } }. 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
- notion-update-database
- Version
- 2.0.1
- App
- Notion
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗