addevent ACTION
Create Event
Creates a new instance of an event. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's addevent account once, then configure and run Create 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: "addevent-create-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
addevent: { authProvisionId: "apn_xxxxxxx" },
title: "Event Title",
startTime: "Start Time",
},
})
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": "addevent-create-event",
"configured_props": {
"addevent": { "authProvisionId": "apn_xxxxxxx" },
"title": "Event Title",
"startTime": "Start Time"
}
}'// 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": "addevent",
},
},
},
)
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: "addevent-create-event",
arguments: {
title: "Event Title",
startTime: "Start Time",
},
})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 event. Required |
startTime Start Time | string | The start date & time of the event. Accepts datetimes in the following formats: YYYY-MM-DD hh:mm:ss e.g. 2023-11-28 10:00:00, YYYY-MM-DD hh:mm e.g. 2023-11-28 10:00, YYYY-MM-DD e.g. 2023-11-28 Required |
endTime End Time | string | The end date & time of the event. Accepts datetimes in the following formats: YYYY-MM-DD hh:mm:ss e.g. 2023-11-28 10:00:00, YYYY-MM-DD hh:mm e.g. 2023-11-28 10:00, YYYY-MM-DD e.g. 2023-11-28. Defaults to datetime_start + 1 hour if not set. Optional |
timezone Timezone | string | The event's timezone. This ensures that the event appears at the correct time for users regardless of their timezone. Defaults to the calendar's timezone if not provided. Optional Dynamic |
location Location | string | The event's location. This can be an address or a URL. Optional |
description Description | string | The event's description. Optional |
calendarId Calendar ID | string | The ID of the calendar that this event will be associated with. Optional Dynamic |
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
- addevent-create-event
- Version
- 0.0.2
- App
- addevent
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗