LeedsApp← All integrations

Microsoft Forms

Through Zapier / Pabbly · 15 min

Microsoft Forms responses arrive as leads in the project

Before you start

A Microsoft 365 work or school account, and a Power Automate Premium licence (the HTTP step is Premium).
Steps use Power Automate, which comes with Microsoft 365. Zapier and Make also have a Microsoft Forms trigger and work the same way (trigger, then a POST to the lead URL).

Your Microsoft Forms lead URL

Your lead URL appears here when you open this page from the LeedsApp app: open the project, then Lead integrations and Microsoft Forms.

Set it up in Microsoft Forms

1
Create a flowGo to make.powerautomate.com, click Create and choose Automated cloud flow. Pick the trigger When a new response is submitted (Microsoft Forms) and click Create.
2
Choose your formIn the trigger, pick your form in Form Id.
3
Get the answersClick + under the trigger and choose Add an action (classic designer: + New step). Add Get response details (Microsoft Forms), pick the same form, and for Response Id pick Response Id from the dynamic content list.
4
Send to LeedsAppAdd an HTTP step. Method POST, URI = your LeedsApp lead URL, header Content-Type = application/json. In Body, type the JSON shown under "What is sent" and replace each value with the matching answer from the dynamic content list.
5
Save and testClick Save, then Test › Manually. Submit your form once. The run history should show every step green and the HTTP step with status 200.

What LeedsApp saves

Microsoft Forms sendsSaved on the lead asnameNamephoneMobile numberemailEmailcityCityAny other keyCustom field
Lead source: Microsoft Forms. You choose what is sent in the Body, so keep the keys name, phone, email and city. The same response sent twice is saved once.

If leads don't arrive

  • The Microsoft Forms trigger only works with a work or school account, not a personal Outlook account.
  • If the HTTP step asks you to upgrade, your licence does not include Premium connectors.
  • Open the flow's run history: a red step shows the exact error.
  • Put quotes around every value in the Body so it stays valid JSON.
  • A 400 reply saying The mobile number is not valid means the phone answer was not a real mobile number. Map the phone question, not another field.

Need help? Write to support@leedsapp.com