Teamup ACTION
Create Event
Creates a new event on a specified calendar. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Teamup 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: "teamup-create-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
teamup: { authProvisionId: "apn_xxxxxxx" },
calendarKey: "Calendar Key",
subCalendarIds: ["Sub-calendars"],
},
})
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": "teamup-create-event",
"configured_props": {
"teamup": { "authProvisionId": "apn_xxxxxxx" },
"calendarKey": "Calendar Key",
"subCalendarIds": ["Sub-calendars"]
}
}'// 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": "teamup",
},
},
},
)
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: "teamup-create-event",
arguments: {
calendarKey: "Calendar Key",
subCalendarIds: ["Sub-calendars"],
},
})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 |
|---|---|---|
calendarKey Calendar Key | string | Key associated with a calendar. Calendar keys are managed using the Web-based calendar settings application. Look for the Sharing tab. Required |
subCalendarIds Sub-calendars | string[] | Array of sub-calendar identifiers Required Dynamic |
title Title | string | Title of the event Required |
startDate Start Date | string | Start Date of the event in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ. Required |
endDate End Date | string | End Date of the event in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ. Required |
location Location | string | Location of the event Optional |
notes Notes | string | Details of the event 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
- teamup-create-event
- Version
- 0.0.2
- App
- Teamup
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗