Teamioo ACTION
Create Calendar Event
Creates a new calendar event. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Teamioo 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: "teamioo-create-calendar-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
teamioo: { authProvisionId: "apn_xxxxxxx" },
eventType: "Event Type",
title: "Title",
},
})
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": "teamioo-create-calendar-event",
"configured_props": {
"teamioo": { "authProvisionId": "apn_xxxxxxx" },
"eventType": "Event Type",
"title": "Title"
}
}'// 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": "teamioo",
},
},
},
)
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: "teamioo-create-calendar-event",
arguments: {
eventType: "Event Type",
title: "Title",
},
})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 |
|---|---|---|
eventType Event Type | string | The type of the event, either 'personal', 'group' or 'office' Required |
title Title | string | Event title. Required |
start Start | string | Start DATE of the event. Time fragment of this datetime is ignored. Required |
end End | string | End DATE of the event. Time fragment of this datetime is ignored. Optional |
startTime Start Time | string | If present, time part of datetime indicates start time of the event. If omitted, the event is considered to be an "all day" event. Optional |
endTime End Time | string | If present, time part of datetime indicates end time of the event. StartTime parameter must be present as well. Optional |
note Note | string | The event note (markdown supported). Optional |
privacyLevel Privacy Level | string | Visibility of the event. This does not apply to "group" calendar events. Optional |
location Location | string | Where the event takes place. Optional |
invitedUsers Invited Users | string[] | Users invited to participate in the event. Each invited user receives an notification which he/she has to accept or reject. Optional Dynamic |
connectedUsers Connected Users | string[] | Users connected to this event. Combines well with calEventType. Only for "office" events. Optional Dynamic |
taggedUsers Tagged Users | string[] | Tagged users - ignored in private tasks. Optional Dynamic |
tags Tags | string[] | Teamioo tags. 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
- teamioo-create-calendar-event
- Version
- 0.0.2
- App
- Teamioo
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗