logo
search
Calendar Problems

Fix InvalidTemplate Error Creating Outlook Events from Microsoft Forms

Algirdas JasaitisAlgirdas Jasaitis Oct 12, 2026 870 views

Question details

The user is encountering an InvalidTemplate error in Power Automate when attempting to create an all-day Outlook calendar event using data submitted through Microsoft Forms.

How to Fix InvalidTemplate Error When Creating All-Day Outlook Events via Power Automate
Product
Power Automate, Microsoft Forms, Outlook
Device & OS
not provided
Scenario
Automating the creation of all-day Outlook events based on Microsoft Forms responses.
Observed behavior
The Power Automate flow fails with an InvalidTemplate error because the Outlook Create Event action is receiving a null or improperly formatted value for the start or end time.
Before you start

Ensure that your Microsoft Forms document includes mandatory date fields so that the Power Automate flow always receives valid date submissions instead of null values.

Solution 1Recommended

Verify Date Field Values and Map Them Correctly

Ensure the start and end dates from Microsoft Forms are marked as required and correctly passed to the Outlook Create Event action to prevent null values.

Power Automate requires explicitly formatted date and time values to successfully generate Outlook events. If an end-date field is left blank in Microsoft Forms, the flow attempts to process a null value, resulting in an InvalidTemplate error.

1
Make form date fields mandatory

Open your Microsoft Form in edit mode. Select the date fields required for the event (such as Start Date and End Date) and toggle the 'Required' switch on.

2
Open flow in edit mode

Navigate to your Power Automate dashboard and open the flow that connects your Microsoft Form to Outlook in Edit mode.

3
Map dynamic content correctly

Locate the 'Create Event (V4)' action. Click on the Start time and End time fields, and use the Dynamic Content menu to map the exact date fields from your Form's response.

4
Configure all-day setting

For all-day events, ensure the 'Is all day event' toggle is explicitly set to 'Yes'. Save your flow and run a test submission from the form.

Verify Date Field Values and Map Them Correctly
Pro Tip: You can use the formatDateTime() expression in Power Automate to ensure dates from Microsoft Forms are converted strictly into the ISO 8601 format that Outlook expects.
Free Microsoft Office alternative

Manage Your Schedules and Documents with WPS Office

While complex cloud integrations require tools like Power Automate, WPS Office offers a seamless, highly compatible solution for your daily document creation and schedule management without the hefty subscription fees.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the installer for your operating system.
  2. 2. Install the software: Run the setup file and follow the on-screen instructions to install WPS Office on your device.
  3. 3. Open and edit files: Launch WPS Office to easily open, edit, and save your documents, spreadsheets, and schedules with full Microsoft format compatibility.
Highly compatible with Microsoft Excel, Word, and PowerPoint file formats.Built-in spreadsheet templates for easily managing project schedules and personal calendars.Free, lightweight, and easy to use across Windows, Mac, and mobile devices.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Power Automate throw an InvalidTemplate error for Outlook events?

This error usually occurs when the flow passes a null or incorrectly formatted value into a mandatory field, such as the start or end time of the calendar event. Ensure your source data contains valid information.

How do I format dates for all-day events in Power Automate?

All-day events require valid date strings, typically in ISO 8601 format (e.g., YYYY-MM-DD). Using the formatDateTime() expression in your flow can help ensure the date from Microsoft Forms is converted correctly.

Do I need to provide an end time for an all-day Outlook event?

Yes. Outlook requires both a valid start time and an end time to successfully generate any calendar event, even if the event is configured to span the entire day.