Skip to content
Forms & SurveysReal-timeUpdated May 2026

Microsoft Forms

Microsoft Forms response reads

Microsoft Forms is the form-builder bundled with Microsoft 365 — used by orgs already in the Microsoft ecosystem for internal surveys, registration forms, quizzes. Tiny Command exposes one action, no triggers (Microsoft Graph supports form-response webhooks via subscriptions; configure for trigger-shaped workflows): List Responses (paginated responses for a specific form). The connection uses Microsoft Graph OAuth with Forms.Read.All scope. For Microsoft-shop workflows that need to process form responses (route them to SharePoint lists, fire follow-up emails via Outlook, sync to other systems), Microsoft Forms + Microsoft Graph is the integration. Microsoft Forms is intentionally simpler than dedicated form builders (JotForm, Typeform); for richer forms, those alternatives are better.

0triggers
1action
≈ 2 minto set up
Freetier · no card
Actions

Do anything Microsoft Forms can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

ActionWhat it does
List Microsoft Forms ResponsesPaginated responses for a specific form. For backfill workflows or for batch-processing of all responses periodically.
Recipes

Pre-built Microsoft Forms workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Microsoft Forms once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Microsoft Forms field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Microsoft Forms integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Microsoft Forms to Tiny Command?
Open the Tiny Command workflow builder, drop in a Microsoft Forms node, and click Connect. Authorize Microsoft Forms once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.
What Microsoft Forms triggers does Tiny Command support?
Tiny Command focuses on outbound actions for Microsoft Forms today. Use Tiny Command's universal Webhook or Schedule trigger to start Microsoft Forms workflows, then run any Microsoft Forms action you need.
What Microsoft Forms actions can I run from a workflow?
1 Microsoft Forms action are available out of the box, covering forms & surveys operations like "List Microsoft Forms Responses". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.
Is the Microsoft Forms integration real-time?
Microsoft Forms actions execute synchronously inside your workflow. Tiny Command waits for Microsoft Forms's API to confirm before continuing to the next step, so downstream nodes can rely on the result.
Do I need to write code to use Microsoft Forms with Tiny Command?
No. Every Microsoft Forms trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Microsoft Forms API endpoint directly.
How much does the Microsoft Forms integration cost?
There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Microsoft Forms integration itself has no per-app surcharge.
Related

More forms & surveys apps people connect.

Same category as Microsoft Forms, ordered by how often teams pair them. Hover the carousel to pause.

Do more with Microsoft Forms.

Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.