Skip to main content

Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Outlook Calendar connector page.

How StackOne sets up Outlook Calendar webhooks

Nothing needs configuring in Outlook or Azure. When you connect an account with events enabled, StackOne creates a Microsoft Graph change-notification subscription automatically and deletes it again when the connection is removed. A single subscription carries every event you enable.

1

Check the calendar permission is granted

A calendar subscription needs Calendars.Read, the same permission the connector already uses to read calendars and events. No webhook-specific permission has to be added, and a connection granted Calendars.ReadWrite already satisfies it.

  • If the connection can list calendar events today, it can receive calendar webhooks.
2

Check which calendar is covered

The subscription is created against the mailbox of the user who authorized the connection, so it reports changes to that user’s calendars only. To follow another user’s calendar, connect an account authorized by that user.

3

Connect the account again when the subscription expires

Microsoft Graph expires calendar subscriptions after at most seven days, and StackOne does not renew them. Delivery stops silently when the subscription lapses — no error is raised, events simply stop arriving.

  • Reconnect the account to create a fresh subscription and resume delivery.
  • Reconnecting also removes the previous subscription, so no duplicates are left behind.

Available webhook events

Outlook Calendar emits three event types, covering the lifecycle of a calendar event. Only events selected in StackOne are dispatched to your application.

1

Enable calendar event events

Events covering calendar events in the connected user’s mailbox. A meeting invitation that lands on the calendar raises the same events as an event the user creates.

  • Event Created (event_created) — Fired when a calendar event is created.
  • Event Updated (event_updated) — Fired when a calendar event changes, including a change to its time, its subject, or an attendee’s response.
  • Event Deleted (event_deleted) — Fired when a calendar event is deleted. Cancelling a meeting the user organizes removes it from the calendar and raises this event too.
2

Retrieve the event to see what changed

A notification identifies what changed rather than carrying it. Each one holds the id of the calendar event, so read the full record with Get My Calendar Event using that id when you need the event’s contents.

3

Review how often notifications arrive

Microsoft Graph delivers at least once, and a single edit can raise several Event Updated notifications as Exchange revises the record. Deleting an event also raises an update before the deletion, because the event is first moved to Deleted Items.

  • Treat each notification as a signal to re-read the event rather than as a change log.
  • Make processing idempotent on the event id so a repeated notification is harmless.

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.