HubSpot ACTION
Create Communication
Log a WhatsApp, LinkedIn, or SMS communication in HubSpot. Put the message fields in Object Properties (
hs_communication_channel_type = SMS | WHATS_APP | LINKEDIN_MESSAGE, hs_communication_body); hs_communication_logged_from and hs_timestamp are set for you. Optionally associate it with a record via Associated Object Type/ID + Association Type. Example: Object Properties { "hs_communication_channel_type": "SMS", "hs_communication_body": "Reminder: call at 9am" }. Returns the created communication with its id. See the documentation- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's HubSpot account once, then configure and run Create Communication 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: "hubspot-create-communication",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
hubspot: { authProvisionId: "apn_xxxxxxx" },
toObjectType: "Associated Object Type",
toObjectId: "Associated Object",
},
})
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": "hubspot-create-communication",
"configured_props": {
"hubspot": { "authProvisionId": "apn_xxxxxxx" },
"toObjectType": "Associated Object Type",
"toObjectId": "Associated Object"
}
}'// 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": "hubspot",
},
},
},
)
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: "hubspot-create-communication",
arguments: {
toObjectType: "Associated Object Type",
toObjectId: "Associated Object",
},
})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 |
|---|---|---|
toObjectType Associated Object Type | string | Type of object the communication is being associated with Optional Dynamic |
toObjectId Associated Object | string | ID of object the communication is being associated with Optional Dynamic |
associationType Association Type | integer | A unique identifier to indicate the association type between the communication and the other object Optional Dynamic |
objectProperties Object Properties | object | Enter the communication properties as a JSON object 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
- hubspot-create-communication
- Version
- 1.0.1
- App
- HubSpot
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗