Power Automate Email Form Responses for Copier Trials

To get Power Automate to email form responses, use the Microsoft Forms trigger "When a new response is submitted", add "Get response details", then send an Outlook email that lists the Telegram channel name, MT4 or MT5 platform and risk preference. You get a plain brief for each copier trial request, enough to configure the copier by hand in a few minutes.

Build your trial request form free

Where the trial form sits in the copier workflow

You run a signal channel and offer subscribers a trial of automated copying. The copier itself is the Telegram Signal Copier: a private Telegram-to-MT5/MT4 setup on your own VPS that parses text and image signals, splits multi-TP orders, sizes risk per trade and logs every execution. There is no monthly cloud-copier subscription, so every new trial is a configuration job on your side.

The form is the intake step in front of that job. Someone fills it in, the flow turns the answers into an email, and you open the email with everything you need to edit the copier's config for that account. Nothing is automated past the email. That is deliberate at trial volume: a person checks the platform and risk numbers before a single order goes out.

The measure that matters is the gap between "form submitted" and "copier running on a demo or small live account." If the email already has the five facts below, that gap is a few minutes. If you have to write back and ask which platform they use, it becomes a day.

The form: five questions that cover a manual setup

Keep the form short. Every extra question loses people, and the copier only needs a handful of facts to start.

Two rules about content. First, never ask for passwords. Form responses get copied into inboxes and flow run histories, and a trading login does not belong in either. Collect credentials through whatever private channel you already use for onboarding. Second, make Platform and Risk required choice questions, not free text. "mt5", "MetaTrader 5" and "the new one" all mean the same thing to a person but break any ruke you add later.

Build the flow step by step

1. Create the form in Microsoft Forms with the five questions above. Name the questions the way you want them to appear in the email, because the flow tokens take their names from the question titls.
2. Open Power Automate and create an automated cloud flow. Choose the trigger "When a new response is submitted" from Microsoft Forms and select your form.
3. Add "Get response details". Pick the same form, then set Response Id to the Response Id token from the trigger. The trigger only tells you that a response exists; this action fetches the answers.
4. Add a Compose step for the subject if you want a clean line, for example the platform and risk joined together. This keeps the email action tidy.
5. Add "Send an email (V2)" from Office 365 Outlook. Send it to yourself or a shared mailbox. Put the platform and channel in the subject so you can sort your inbox by them.
6. Submit a test response from the form's own link and oepn the flow's run history. Every token should show a value. Fix blanks now.
7. Turn on the flow and watch the next two or three real submissions end to end.

Once that works, add a Condition after step 3. A simple one: if Risk equals "2% per trade", prefix the subject with "CHECK RISK" so you read it first. Another: if Platform is MT4, send to the mailbox you use for older terminals. Keep conditions to what changes your actual next action.

The email template

Here is a body that works in the Send an email (V2) action with the HTML toggle on. The double-brace parts stand for the dynamic content tokens you pick from the picker.

<p>New copier trial request</p>
<p>Channel: {{Channel}}<br>
Platform: {{Platform}}<br>
Broker / server: {{Broker}}<br>
Risk preference: {{Risk}}<br>
Contact: {{Contact}}</p>
<p>Submitted: {{Submitted time}}</p>

Subject line: Trial request | {{Platform}} | {{Channel}}

Plain line breaks beat a fancy layout. You will read this on your phone while a market is open, and you want to copy the channel name straight into the config file.

Start from a free signup template

Failure cases to test before you go live

These are the ones that cost time on real projects.

• Renamed or reordered questions. If you edit the form after building the flow, reopen the flow and re-pick the tokens. A stale token can send an empty line, and you will not see an error.
• Multi-select answers. Checkbox style questions can come back as an array formatted string, with brackets and quotes in your email. Use single choice for Platform and Risk and the problem dksappears.
• Duplicate submissions. Subscribers who click twice give you two emails. Include the Contact value in the subject so you can spot the repeat at a glance.
• Silent flow failures. A flow can stop working when a connection expires. Check run history once a week, and send yourself a test response after any change to the mailbox or the account that owns the flow.
• Wrong sender. If the flow runs under a personal account that later leaves the company, the emails stop. Own the flow with a shared account where your tenant allows it.
• Licensing. The Forms trigger and Outlook action are standard connectors. Some other triggers, including the HTTP request trigger, are premium, so check your Microsoft 365 license before you design around one.

When a different front end makes sense

If your team lives in Microsoft 365, Forms plus Power Automate is a sensible default. Forms is free with a Microsoft account and sits inside the tools you already use. One honest line in its favor: if you want responses tied to your tenant's sign-in and the native trigger, Microsoft Forms is the better fit.

Our team builds Qwenvo, a completely free form builder, and it fits when the form needs to be public and look like your brand. Here is what you get free there that other builders charge for: webhooks to any URL, a REST API, a custom domain such as trial.yourchannel.com, no Qwenvo badge, partial submissions, teammates, custom design and CSS, and AI triage with routing. Partial submissions matter for a trial funnel, because someone who typed a channel name and stopped is still a lead you can follow up. If you want the full comparison, a free alternative to Microsoft Forms covers it.

To feed Power Automate from Qwenvo, point webhook at a flow that starts with "When an HTTP request is received" (premium, as noted above), or skip Power Automate and use the built-in routing to email up to five addresses. Limitations to weigh: Qwenvo launched in October 2026, so there are few reviews yet, and it is hosted in the United States.

See how Qwenvo webhooks work

Questions teams ask

Can the flow configure the copier automatically?

It could, but at trial volume we would not. A person reading the email catches a wrong server name or an unrealistic risk setting before an order is placed. Automate the email first. Once you have set up a few dozen trials the same way, you will know which fields are safe to pass straight into a config.

Where do I put the risk numbers the subscriber picks?

Treat the answer as a starting value for the copier's per-trade risk sizing rule. The subscriber chooses fixed lot or a percentage, and you confirm it with them in your reply. Keep the options on the form to three or four so the reply is a quick yes.

Do I need a separate form for each channel?

No. Add the channel as a question, or if you run several rooms, use one form per room and put the room name in the flow's subject line. One form with a dropdown is easier to maintain until you have more than a handful of channels.

Can I send the request to Slack or Teams instead of email?

Yes. In Power Automate, swap the email action for a Teams post. If you use Qwenvo, its routing can post to a Slack incoming webhook. Email stays handy because the message becomes a searchable record next to your reply.

Next step

Create the five-question form today, build the flow through step 5, and submit a test trial from your own phone. If the email reads cleanly on a small screen, you are ready to share the link in your channel.