Dynalist ACTION
Insert Document Content
Inserts content to a specific document. If the document has existing content, the new content will be appended. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Dynalist account once, then configure and run Insert Document Content 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: "dynalist-insert-document-content",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
dynalist: { authProvisionId: "apn_xxxxxxx" },
documentId: "Document ID",
parentId: "Parent 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": "dynalist-insert-document-content",
"configured_props": {
"dynalist": { "authProvisionId": "apn_xxxxxxx" },
"documentId": "Document ID",
"parentId": "Parent 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": "dynalist",
},
},
},
)
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: "dynalist-insert-document-content",
arguments: {
documentId: "Document ID",
parentId: "Parent 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 |
|---|---|---|
documentId Document ID | string | The ID of the document. Required Dynamic |
parentId Parent ID | string | The ID of the parent item to insert under. Required Dynamic |
index Index | integer | This field is an integer that's the zero-indexed position you want the file to land in the parent folder, supply -1 to place it at the end, and 0 to place it at the top. Required |
content Content | string | The new item title. Required |
note Note | string | The new item note. Optional |
checked Checked | boolean | The new item checked status. Optional |
checkbox Checkbox | boolean | Whether the new item should be a checklist. Optional |
heading Heading | integer | What heading level is new item, from level 1 to level 3. Default is 0 Optional |
color Color | integer | What color label does the new item have, from color 1 to 6. Default is 0. 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
- dynalist-insert-document-content
- Version
- 0.0.3
- App
- Dynalist
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗