HubSpot ACTION
Create Meeting
Create a meeting engagement in HubSpot. Put meeting fields in Object Properties (
hs_meeting_title, hs_meeting_body, hs_meeting_start_time, hs_meeting_end_time as ISO-8601); hs_timestamp defaults to the start time. Set Associated Object Type and optionally link a record via Associated Object ID + Association Type. Example: Object Properties { "hs_meeting_title": "Kickoff", "hs_meeting_start_time": "2026-08-27T14:00:00Z", "hs_meeting_end_time": "2026-08-27T15:00:00Z" }. Returns the created meeting 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 Meeting 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-meeting",
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-meeting",
"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-meeting",
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 meeting is being associated with Required Dynamic |
toObjectId Associated Object | string | ID of object the meeting is being associated with Optional Dynamic |
associationType Association Type | integer | A unique identifier to indicate the association type between the meeting and the other object Optional Dynamic |
objectProperties Meeting Properties | object | Enter the meeting properties as a JSON object. Required properties: hs_meeting_title, hs_meeting_body, hs_meeting_start_time, hs_meeting_end_time. Optional: hs_meeting_status 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-meeting
- Version
- 1.0.1
- App
- HubSpot
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗