Skip to content
Nappai Documentation

OutlookCalendarWebhook

The OutlookCalendarWebhook component allows you to monitor your Microsoft Outlook calendar for any changes. It acts as a listener that detects when events are created, updated, or deleted, and passes this information to your workflow so you can automate actions based on those calendar changes.

How it Works

This component connects to the Microsoft Graph API to check for updates in your Outlook calendar. It uses a polling method that periodically checks for new or modified calendar events based on your configuration.

When a change is detected, the component processes the raw data and converts it into a structured format that other nodes in your Nappai workflow can understand. It ensures that only the relevant events and calendars you are interested in are processed, filtering out noise and preparing the data for downstream automation. The component supports listening to specific types of events, such as creations, updates, or deletions, allowing you to tailor the workflow to your needs.

Connection & Credentials

This component requires configuring a credential in the Nappai panel before interacting with the external service:

  1. Go to the Credentials section in your Nappai panel.
  2. Create a new credential of the type Microsoft Outlook and fill in the required fields (Client ID, Client Secret, Tenant ID).
  3. In your workflow, select the saved credential in the Credential input field of this node.

Inputs

Input Fields

The following fields are available to configure this component:

  • Calendar: Select the Outlook Calendar to monitor for event changes. Use the refresh button to update the list of available calendars dynamically.
  • Events: Select the types of calendar events you want the component to track. You can choose between Event Created (new events), Event Updated (modifications), and Event Deleted (removals). If you leave this empty, the component will listen to all types of changes by default.

Outputs

This component produces structured data about the calendar events it detects. The output contains a readable summary and a detailed dictionary with all event information, which you can connect to other nodes to trigger automations.

Output Data Example (JSON)

json { “text”: “[Created] Team Standup Meeting”, “data”: { “eventId”: “AAMkADAxNTg2…”, “subject”: “Team Standup Meeting”, “start”: “2024-05-20T09:00:00Z”, “end”: “2024-05-20T10:00:00Z”, “status”: “confirmed”, “organizer”: “user@example.com” } }

Connectivity

This component is designed to trigger workflows based on calendar changes. Its output is typically connected to:

  • Agent Nodes: To analyze event details and make decisions based on the calendar data.
  • Storage Nodes: To save calendar event details to a database, spreadsheet, or file.
  • Notification Nodes: To send alerts or messages when specific events are created, updated, or deleted.

This node acts as the starting point for event-driven automations, ensuring your workflow reacts instantly to updates in your Outlook calendar.

Usage Example

Scenario: Auto-create Tasks for New Meetings

You can use this component to automatically create tasks in a project management tool whenever a new meeting is added to your Outlook calendar.

  1. Configure the Calendar input to select the calendar you want to monitor (e.g., “Work Calendar”).
  2. In Events, select Event Created to only react when new events appear.
  3. Connect the Data output to a code node or an agent that parses the event subject and duration.
  4. Connect the result to a node that creates a task in your project management app.

Now, whenever you add a meeting to your Outlook calendar, Nappai will automatically generate a corresponding task for your team.

Tips and Best Practices

  • Use the Events filter to reduce processing load by only listening to the changes you actually need.
  • Ensure your Microsoft Outlook credential has sufficient permissions to read calendar data for the selected calendar.
  • The Calendar dropdown supports dynamic updates; click the refresh button if your calendars don’t appear immediately.
  • This component works best with downstream nodes that can handle structured JSON data containing event metadata like subject, start time, and status.
  • If you only need to react to specific calendar types, always select them in the Events field to avoid unnecessary processing of unwanted events.

Security Considerations

  • Credential Management: This component uses a Microsoft Outlook credential to access your calendar securely. Never share or expose the Client Secret or Tenant ID in your workflow files or logs.
  • Data Privacy: The component processes calendar data via the Microsoft Graph API. Ensure your workflow only exposes sensitive calendar information to trusted downstream nodes.
  • Access Control: Verify that the account linked to the credential has the appropriate permissions to access the selected calendar.
  • Webhook Safety: This component operates as a listener within Nappai. Ensure your automation flows do not expose sensitive calendar data to unverified external endpoints.