Definition

The "Find Event" action allows you to retrieve detailed information about a specific event in a Microsoft Calendar by using its Event ID. This is especially useful when you want to fetch or verify an event's content, timing, location, attendees, and recurrence settings—whether for internal review, audit logs, or follow-up workflows.

Key capabilities of this action include:

Accessing full metadata of a calendar event (title, time, location, etc.)
Viewing organizer and attendee information, including response statuses
Checking reminders, visibility, and busy/free status
Retrieving recurrence patterns for repeating events
Accessing the full event body and a direct Outlook event link

This action helps ensure consistency, auditability, and seamless integration with your scheduling and automation flows.

Example Use Cases

1. Validate an Event Before Making Updates

Before modifying or deleting a Microsoft Calendar event, use this action to retrieve and confirm key details such as subject, time, and attendees—ensuring accuracy in your automation flow.

2. Monitor Attendee Responses for Key Meetings

Automatically check if all required participants have responded to a meeting invitation by retrieving the event’s attendee list and response statuses, enabling follow-up actions if necessary.

3. Generate Internal Meeting Summaries or Logs

Use this action to retrieve full event details like description, body content, location, and organizer info—then generate logs or summary emails for record-keeping or internal reporting.

4. Check Calendar Status Before Scheduling a Follow-Up

Pull the availability setting (Busy/Free/OOF) of an event to determine if a user is available for another follow-up action, such as triggering a notification or booking a second session.

5. Access Recurring Event Configurations

If you need to replicate or analyze the recurrence pattern of a meeting series, this action provides structured data about how and when the event repeats—useful for pattern-based logic or cloning.

6. Trigger Workflows Based on Specific Meeting Details

Fetch and evaluate elements like event importance, visibility, or subject to trigger conditional logic in a flow (using Subflow Trigger)—ideal for automated prioritization or escalation.

📥 Inputs

Each field is explained in detail to ensure you understand its purpose and how to use it effectively.

1. Connection

This field represents your authenticated Microsoft account connection. It is necessary to authorize and enable the action to retrieve calendar events from your Microsoft Calendar.If you haven’t connected your Microsoft account yet, you will be prompted to log in and grant the necessary permissions.

2. Calendar

Select the calendar from which you want to retrieve the event.Microsoft accounts may contain multiple calendars (e.g., Work, Personal, Shared calendars), and this field allows you to specify the exact one that contains the event you're looking for.The list of calendars will be fetched automatically once the connection is established.

3. Event ID

Enter the unique identifier of the event you wish to retrieve.Each calendar event in Microsoft Calendar has an internal ID that distinguishes it from other events. This ID is required to locate and retrieve the exact event details.You can obtain this ID from a previous action (e.g., after creating or listing events) or from an external system that stores it.

🛈 Tip: You can use dynamic data from earlier steps in your flow to pass the event ID automatically.

📤 Outputs

Once the event is successfully retrieved using the “Find Event” action, the following data fields are returned. These outputs provide full visibility into the event's metadata, structure, and attendees, which can be reused in later steps of your flow.

1. Event ID

A unique identifier for the retrieved event. This ID helps reference the event in future actions, such as updating or deleting it.

2. Event Link

A direct URL to open the event in Outlook on the web. This is helpful if you want to provide a clickable link for users or review the event manually.

3. Subject

The title or name of the event, as originally set in the event creation. Helps identify the event quickly at a glance.

4. Created Time

The exact date and time when the event was initially created in the calendar.

5. Last Modified Time

Indicates when the event was last changed. Useful for understanding the latest update or version of the event.

6. Change Key

A version marker used internally by Microsoft to track changes to the event. This ensures consistency when performing operations like updates.

7. iCalendar UID

A global identifier compliant with the iCalendar standard, useful for synchronizing recurring events across different calendar systems.

8. Reminder Minutes Before Start

Specifies how many minutes before the event the reminder will trigger. For example, 15 means the user will be alerted 15 minutes in advance.

9. Is Reminder On

A boolean field indicating whether a reminder is set for the event (true/false).

10. Body Preview

A short snippet or preview of the event’s body content or description, giving a quick summary of what's included.

11. Importance

Reflects the priority of the event. Possible values are low, normal, or high. This helps in categorizing or styling event data accordingly.

12. Visibility

Defines how private or public the event is to others with calendar access. Options include:

normal: Fully visible
personal: Informational, not private
private: Details hidden
confidential: Highly restricted visibility

13. All Day Event

Returns true if the event is set as an all-day event. Otherwise, it will return false.

14. Is Organizer

Indicates whether the current user is the organizer of the event (true/false).

15. Response Request

Specifies if attendees are expected to RSVP to the event.

16. Busy/Free

Indicates how the event blocks the calendar:

free
busy
tentative
oof (Out of Office)
workingElsewhere
unknown

17. Event Type

Shows what kind of event this is:

singleInstance: A standalone event
occurrence: Part of a recurring series
exception: A modified instance of a recurring event
seriesMaster: The recurring event template

18. Start

Details about when the event begins:

DateTime: Full start date and time
Date: If all-day, only the date (yyyy-mm-dd)
TimeZone: Time zone context for accurate scheduling

19. End

Details about when the event ends:

DateTime: Full end date and time
Date: For all-day events
TimeZone: Time zone for end time

20. Attendees

Details for each invited person:

Type: required, optional, or resource
Status: The response (e.g., accepted, declined)
Response Time: When they replied
Display Name: Their name (if available)
Email Address: Contact email

21. Organizer

Information about the person who created or owns the event:

Display Name: Organizer’s name
Email: Their email address

22. Repeat

Pattern and range of recurrence if the event repeats:

Pattern:

Type: daily, weekly, absoluteMonthly, etc.
Interval: Frequency (e.g., every 2 days)
Month / Day of Month / Days of Week / Week Index / First Day of Week: Specific rules

Range:

Type: endDate, noEnd, numbered
Start Date: When the repetition begins
End Date / Number of Occurrences: When it stops
Time Zone: For accurate range scheduling

23. Status

The current user's status in relation to the event (e.g., accepted, declined).

Type: Response type
DateTime: Time of response

24. Body Content

Full content of the event description:

Content Type: Either text or html
Content: The actual body content

25. Primary Location

The main location where the event will take place:

Display Name: Name or address
Location Type: e.g., conferenceRoom, homeAddress
Unique ID: Internal location identifier
Unique ID Type: Source of the location (directory, private, etc.)

26. Additional Locations

List of other specified locations for the event. Each includes:

Display Name
Location Type
Unique ID
Unique ID Type

🧪 Example: Fetch Event Details to Send Confirmation Email

Scenario

You’re running an automated workflow in a customer engagement platform. After a customer books a meeting using a scheduling tool (e.g., Microsoft Bookings or a form), you want to automatically pull event details from the Microsoft Calendar and send them a confirmation email with the relevant information (title, date, time, and location).

Step-by-Step Setup

1. Trigger the Flow

Start the flow using a trigger like:

“Form Submitted”
“When a New Event is Created” (optional)

2. Add "Find Event" Action

Use the Microsoft Calendar → Find Event action to fetch full details of the booked event.

Fill in the input fields:

Connection: Select your Microsoft Calendar connection.
Calendar: Choose the calendar that the event was saved to (e.g., “Bookings Calendar”).
Event ID: Pass the event ID from the previous step (e.g., from the form or booking app).

3. Use Output Data

Once the event is retrieved, use its output values in subsequent steps. For example:

Subject → “Meeting with [Customer Name]”
Start Date/Time → Format to readable form for email
Primary Location → Display Name → “Microsoft Teams Link” or a physical address
Event Link → Include as a CTA ("View on Calendar")

4. Send Email

Add an email step (e.g., Outlook, Gmail, SendGrid) and inject dynamic content from the Find Event output to compose a professional, automated confirmation email.

✅ Result

Your customer immediately receives a personalized confirmation email with accurate and real-time details pulled directly from your Microsoft Calendar. This reduces manual follow-ups, prevents errors, and ensures customers have what they need.