View as Markdown
Notion icon

Notion ACTION

Delete Block

Sets a Block object, including page blocks, to archived: true using the ID specified. Example: blockId "1a2b3c4d-..." → archives that block and returns the block object with archived: true. See the documentation
  • Action
  • Writes data
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Notion account once, then configure and run Delete Block 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-delete-block",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    notion: { authProvisionId: "apn_xxxxxxx" },
    blockId: "Block ID",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Delete Block inputs
Property Type Description
blockId Block ID string
The ID of the block to act on, e.g. 1a2b3c4d-5e6f-7890-abcd-ef1234567890 (a 32-character UUID, with or without dashes). A Notion page is itself a block, so this can also be a page ID. Use the Search action to resolve a page name into an ID, or the Retrieve Page Content action to list the child block IDs within a page.
Required

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-delete-block
Version
0.0.12
App
Notion
Authentication
OAuth
Read-only
No
Destructive
No
Open world
Yes