Microsoft Outlook Calendar TRIGGER
Calendar Event Deleted (Instant)
eventId), changeType, subscriptionId, tenantId, and notificationTimestamp. Downstream processors must rely solely on this metadata. See the documentation- Trigger
- Polling
- OAuth
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Microsoft Outlook Calendar account, configure the source, and choose the webhook where your backend receives events.
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 deployed = await pd.triggers.deploy({
id: "microsoft_outlook_calendar-deleted-calendar-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
microsoft_outlook_calendar: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
userId: "User ID",
},
webhookUrl: "https://example.com/webhooks/microsoft-outlook-calendar",
})
console.log(deployed.id)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "microsoft_outlook_calendar-deleted-calendar-event",
"webhook_url": "https://example.com/webhooks/microsoft-outlook-calendar",
"configured_props": {
"microsoft_outlook_calendar": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"userId": "User ID"
}
}'MCP servers expose Microsoft Outlook Calendar actions as on-demand tools.
Calendar Event Deleted (Instant) is an event source, so your application deploys it
with the Connect SDK or API and then either receives each event at a
webhook URL or retrieves events on demand with the trigger events API.MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.
SCHEMA
Configuration
These inputs define which events the source watches. Dynamic options are loaded from the connected account.
| Property | Type | Description |
|---|---|---|
timer Webhook renewal timer | $.interface.timer | Graph API expires Outlook notifications in 3 days, we auto-renew them in 2 days, see Required |
userId User ID | string | Optional user ID or principal name for delegated/admin scenarios. When provided, subscribes to /users/{userId}/events instead of /me/events. Optional |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Microsoft Outlook Calendar through Pipedream managed auth.
02
Deploy
Your backend deploys this source with that user's own configuration.
03
Webhook delivery
Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.
OR
On-demand retrieval
No webhook required. Your app or agent can fetch recent events from the trigger events API.
REFERENCE
Trigger details
- Registry key
- microsoft_outlook_calendar-deleted-calendar-event
- Version
- 0.0.1
- App
- Microsoft Outlook Calendar
- Authentication
- OAuth
- Delivery
- Polling source
- Output
- Events emitted by Microsoft Outlook Calendar.
- Source
- View on GitHub ↗