Salesforce ACTION
Create Content Note
Create an enhanced Salesforce content note (rich text, stored in Salesforce Files). Use this rather than Create Note on modern orgs; Create Note writes the classic plain-text note object. Use Update Content Note to edit one afterwards. Notes must be enabled in the org first - see Set Up Notes. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Salesforce account once, then configure and run Create Content Note 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: "salesforce_rest_api-create-content-note",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
salesforce_rest_api: { authProvisionId: "apn_xxxxxxx" },
Title: "Title",
Content: "Content",
},
})
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": "salesforce_rest_api-create-content-note",
"configured_props": {
"salesforce_rest_api": { "authProvisionId": "apn_xxxxxxx" },
"Title": "Title",
"Content": "Content"
}
}'// 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": "salesforce_rest_api",
},
},
},
)
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: "salesforce_rest_api-create-content-note",
arguments: {
Title: "Title",
Content: "Content",
},
})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 |
|---|---|---|
Title Title | string | Title of the content note. Required |
Content Content | string | Body content of the note, as plain text. Any markup characters ( &, <, >, ", ') are HTML-escaped, then the result is base64-encoded before send. Required |
LinkedEntityId Linked Entity ID | string | Optional ID of a record to link this note to (Salesforce's 15- or 18-character record ID, e.g. 001XX000003DHP0 for an Account). Use SOQL Query to find the ID. Optional |
additionalFields Additional Fields | object | Other ContentNote/ContentDocumentLink fields as name -> value pairs. Use for OwnerId, IsReadOnly, etc. - use Describe Object on ContentNote to discover other valid field names. ShareType (V=Viewer, C=Collaborator, I=Inferred permission; default I) and Visibility (AllUsers, InternalUsers, SharedUsers) only take effect when LinkedEntityId is also set - they're ignored otherwise. Example: {"OwnerId": "005xxx", "ShareType": "V", "Visibility": "AllUsers"}. 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
- salesforce_rest_api-create-content-note
- Version
- 1.0.1
- App
- Salesforce
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗