Adhook ACTION
Create Calendar Event
Generates a personalized calendar event in AdHook. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Adhook account once, then configure and run Create Calendar Event 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: "adhook-create-calendar-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
adhook: { authProvisionId: "apn_xxxxxxx" },
title: "Event Title",
description: "Event Description",
},
})
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": "adhook-create-calendar-event",
"configured_props": {
"adhook": { "authProvisionId": "apn_xxxxxxx" },
"title": "Event Title",
"description": "Event Description"
}
}'// 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": "adhook",
},
},
},
)
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: "adhook-create-calendar-event",
arguments: {
title: "Event Title",
description: "Event Description",
},
})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 Event Title | string | The title of the calendar event Optional |
description Event Description | string | The description of the calendar event Optional |
externalId External Id | string | An external Id to the event Optional |
start Start Date | string | Start date of the event. Format: YYYY-MM-DDTHH:MM:SSZ Optional |
end End Date | string | End date of the event. Format: YYYY-MM-DDTHH:MM:SSZ Optional |
allDay All Day | boolean | Whether the event lasts all day or not Optional |
color Color | string | The color of the event Optional |
subtenantId Subtenant Id | string | The id of the subtenant. Optional Dynamic |
tags Tags | string[] | A list of tags. Optional |
topics Topics | string[] | A list of topics. Optional |
attachments Attachments | string[] | A list of objects of attachments for the event. Format: {"name": "Attachment name", "url":"https://attachment.com/file.pdf", "fileExtension":"pdf"} 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
- adhook-create-calendar-event
- Version
- 0.0.2
- App
- Adhook
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗