If you want a simple way to collect registrations and automatically send the right event details, Microsoft Forms and Power Automate are a practical combination. With Microsoft Power Automate, you can capture a response, check the attendee’s preference, and trigger the next action without handling each submission manually.
This is especially useful for webinars, internal meetings, training sessions, demos, and hybrid events. Instead of sorting responses one by one, teams can build a flow that sends the appropriate invite, meeting link, or location details based on the user’s selection.
What this workflow helps you solve
Most teams do not struggle with creating a form. The real problem starts after the response is submitted. Someone has to check the answers, decide which invite to send, copy the meeting details, and make sure nothing is missed.
That is where automation becomes useful.
When you connect Microsoft Forms with Power Automate, you can:
- Collect registrations in one place
- Send the right invite based on the response
- Reduce manual follow-up
- Keep event communication consistent
- Avoid sending incorrect joining details
This is one of the most practical ways to create an automated workflow for Microsoft Forms because it connects data collection with an immediate action.
When to use this approach
This setup is best when one form can lead to different outcomes.
For example:
- Online attendees need a virtual meeting link
- In-person attendees need the venue address
- Different sessions need different time slots
- Internal teams need a copy of the registration data
- Confirmed attendees should receive a proper calendar event
It is also a useful setup if you are looking at how to use Microsoft Forms for event registration in a more structured way.
Read more: How to power automate Microsoft Forms for sending invitations
What you need before building the flow
Before you open Power Automate, make sure a few basics are already clear.
You need:
- A Microsoft Form for registrations
- The attendee email field in that form
- One question that decides what kind of invite should be sent
- Event details ready in advance
- Access to Outlook and Power Automate in Microsoft 365
A simple example is a form question like:
How will you attend this event?
- Online
- In person
That one answer gives the flow enough logic to route the right invite.
Sending calendar invites to attendees from Microsoft Forms based on their response
Before you customize the invite logic, you need to build the flow and connect it to the correct form. This first part makes sure Power Automate can detect every new registration and pull in the submitted answers.
Step 1: Open Power Automate and create a new automated flow
Go to Power Automate and select:
+ Create > Automated cloud flow
This starts a flow that runs automatically whenever a defined trigger happens. In this case, the trigger will be a new response submitted through Microsoft Forms.
If you are setting this up for the first time, make sure you are signed in with the same Microsoft 365 account that has access to the form and the mailbox or calendar you plan to use later.
Step 2: Give the flow a clear and usable name
In the Flow name field, enter a name that clearly explains what the flow is for.
For example:
Send Event Invite from Form Response
A descriptive name matters because you may later create multiple flows for registrations, reminders, approvals, or follow-ups. A vague name like “Test Flow” becomes difficult to manage later.
Step 3: Choose the form submission trigger
In the trigger search bar, type Forms and select:
When a new response is submitted
This trigger tells Power Automate to start the workflow each time someone completes and submits the selected form. This is the point where the registration process moves from data collection into automation.
Once the trigger is selected, click Create.
Step 4: Select the correct Form ID
After the trigger is added, go to the Form ID field and choose the Microsoft Form you want to use.
This step is important because the flow will only monitor the specific form selected here. If you choose the wrong form, the workflow may still run, but it will not capture the right responses.
At this stage, you are linking the registration form directly to the automation logic.
Take control of your business operations
Discover how Confiz services can simplify your complex workflows and improve decision-making.
Get a Free QuoteStep 5: Add a new action to retrieve the submitted answers
Click + New step.
The trigger only tells Power Automate that a new submission happened. It does not automatically show the actual answers entered by the attendee. To use those answers later in the flow, you need a second action that pulls them in.
Step 6: Search for the Forms response action
In the action search box, type Forms again.
From the available actions, choose:
Get response details
This action instructs Power Automate to fetch the full response associated with the new submission.
Step 7: Select the same form again inside “Get response details”
In the Form ID field of this action, select the same registration form you selected in the trigger.
This keeps the trigger and the response retrieval tied to the same form, so the flow reads the correct submission.
Step 8: Map the Response ID from the trigger
In the Response ID field, click into the dynamic content area and choose:
Response ID
This is how Power Automate knows which exact response it should retrieve. Without this field, the flow would know that a form was submitted, but it would not know which submission to read.
Step 9: Add a new step for decision logic
Click + New step again.
Now that the flow can read the form answers, the next step is to check one of those answers and decide what to do next.
This is where the workflow becomes useful for event coordination, as it shifts from simple response collection to response-based action.
Step 10: Add the condition action
Search for Condition and add it to the flow.
The condition is what lets the flow separate online attendees from in-person attendees, or route different responses in different ways. Without this step, every person would receive the same message, even if their choices were different.
Step 11: Review the flow before moving forward
At this point, your flow should have three main parts:
- When a new response is submitted
- Get response details
- Condition
This means the structure is ready. The trigger captures the submission, the second step reads the answers, and the third step is ready to evaluate the attendee’s choice.
Step 12: Save your progress before customization
Before moving on to the response-based invite logic, click Save.
Saving at this stage is a good habit. It protects the work already done and makes it easier to return to the flow if you need to adjust the logic later.
Customize the form based on the response
Now that the flow can capture and read a form submission, the next step is to decide what should happen based on the attendee’s answer. This is the part that allows a single form to support multiple attendance paths.
Step 1: Choose the question that should control the flow
Inside the Condition action, click the first value field and select the form question that should decide what kind of invite is sent.
For example, you might use a question like:
Will you join the event in person?
or
How will you attend this event?
This question should clearly separate attendees into different paths.
Step 2: Set the comparison rule
In the middle field of the condition, choose:
is equal to
This tells Power Platform to compare the attendee’s answer against a specific value.
Step 3: Enter the response value to check against
In the third field, enter the value that should trigger the first branch.
For example:
Yes
or
Online
Depending on how the form question was written. This step matters because the condition must match the response exactly. If the answer in the form is “Online” but the condition checks “Yes,” the wrong branch may run.
Accelerate growth at an unprecedented pace
Discover how Confiz can help you take control of your daily operations, increasing growth and revenue.
Book a Free ConsultationStep 4: Open the “If yes” branch and add an action
Go to the If yes side of the condition and click Add an action.
This branch will handle attendees whose answer matches the value you just defined.
For example, if the condition checks whether the attendance type is “Online,” then the If yes branch will be the path for remote attendees.
Step 5: Search for the Outlook email action
In the action search box, type email.
From the list of available actions, select:
Send an email (V2)
This is the simplest way to send the attendee their event details immediately after the form is submitted.
Step 6: Add the attendee’s email address to the To field
In the To field, select:
Responder’s Email
This pulls the attendee’s email address directly from the submitted form response, so the message goes to the correct person without manual entry.
Step 7: Write a clear subject line
In the Subject field, enter a subject line that clearly tells the attendee what the email is about.
For example:
- Online Event Joining Details
- In-Person Attendance Confirmation
- Training Session Invite
A clear subject line helps attendees recognize the purpose of the email quickly.
Further readings: How to power automate Microsoft Forms for sending invitations
Step 8: Add the correct event details in the email body
In the Body field, write the content the attendee actually needs.
If this branch is for remote attendance, include:
- Event name
- Date and time
- Meeting link
- Joining instructions
- Any notes or materials to review before the session
If this branch is for in-person attendance, include:
- Event name
- Date and time
- Venue address
- Room or floor information
- Reporting or check-in details
- Parking instructions if relevant
The email should be specific to the attendee’s selected option. That is what makes the workflow useful.
Step 9: Repeat the setup in the “If no” branch
Now move to the “If no” side of the condition and add another “Send an email (V2)” action.
Repeat the same setup, but this time write the details for the other attendance type.
This ensures that one branch handles one type of attendee and the other handles the other.
Step 10: Save and test the full flow
Once both branches are complete, click Save.
Then use the Test button in the top-right corner and submit sample responses through the form.
At minimum, test:
- One response that should go to the If yes branch
- One response that should go to the If no branch
Check whether:
- The flow ran successfully
- The correct branch was triggered
- The email reached the right person
- The event details were accurate
- The link, date, time, and location are displayed properly
This final step is important because most workflow issues arise from condition values, dynamic fields, or message content.
Conclusion
Using Microsoft Forms with Power Automate is a practical way to make event coordination more efficient. Instead of manually reviewing responses and sending invites one by one, you can build a workflow that responds automatically and sends the right event details based on each attendee’s selection.
This reduces repetitive admin work, improves accuracy, and creates a more consistent experience for attendees. For teams managing webinars, hybrid events, training sessions, or internal meetings, it is a simple way to connect registration with scheduling and keep the process easier to manage.
If you are looking to improve how your team handles registrations and event invites, contact Confiz at marketing@confiz.com to explore the right approach for your process.
