How to connect Power Automate and Power Apps with the right inputs
By Jordan Ellis Published 11 min read
As an Amazon Associate I earn from qualifying purchases. That costs you nothing and does not decide what gets recommended. We also earn a commission from some links to partner brands (SentryPC, HappyScribe, Sucuri, IceVPN).
On this page (12 sections)
- The short version
- What you need
- Create the flow that the app can call
- Pass named values and return named outputs
- Copyable formulas for flow inputs and outputs
- Pass tables and collections without oversized requests
- Store large files and pass links
- Set run-only users and connections
- Share both the app and the flow
- Troubleshoot failed runs and permission errors
- Choose a practical first workflow
- Questions people still ask
In short: To connect Power Automate and Power Apps, create an instant flow with the Power Apps trigger, add it through the Power Automate pane, and call it from a formula such as MyFlow.Run(). Add Respond to a Power App or flow when the app needs a result. Share both the app and flow, then check run-only connections before other people use it.
Part of our guide on automate weekly invoice emails
Most guides show a flow. This one shows the trigger, input formulas, permissions, payload patterns, and checks that make the connection work.
| Trigger to use | When Power Apps calls a flow |
|---|---|
| Return action | Respond to a Power App or flow |
| Input setup | Add inputs in the Power Apps trigger |
| Large files | Store them in OneDrive or SharePoint and pass a link |
| Table pattern | JSON.stringify in Power Apps, then Parse JSON in the flow |
| Licence check | Review the connector and Power Automate licensing pages |
The short version
- Use the instant Power Apps trigger when an app needs to start a flow and pass values.
- Add named inputs in the trigger and named outputs in Respond to a Power App or flow.
- Configure run-only users and connections before sharing the app with colleagues.
- Pass large files through OneDrive or SharePoint and send a link or file identifier instead.
- Measure your own flow latency and design the app with loading states and error handling.
- Check Microsoft licensing and connector documentation before using premium actions.
What you need
Before building anything, confirm the app and flow use the same Power Platform environment. Permission problems often look like formula errors when the real issue is ownership or a missing connection.
You need edit access to the app and permission to create or edit flows. You also need access to every service the flow will use, such as SharePoint, Outlook, Teams, Excel, Dataverse, or SQL.
- A work or school account supported by your organisation's Power Platform setup
- Power Apps Studio access in the app's environment
- Power Automate access in the same environment
- Permission to use each connector in the flow
- A suitable licence for any premium connector or premium feature
Create the flow that the app can call
Use the instant trigger named When Power Apps calls a flow. It accepts values from a Power Apps formula and is designed for an app-initiated run.
Scheduled and event-based triggers serve different jobs. Use them for background automation, not for a button that must pass form values into the flow. We go through Synology NAS power on step by step elsewhere on the site.
- Open Power Apps Studio and select the app in edit mode.
- Select Power Automate in the left navigation pane.
- Choose Create new flow, or select Add flow if the pane already contains flows.
- Choose the Power Apps trigger. The designer may show it as When Power Apps calls a flow.
- Add the actions the flow should perform after receiving the request.
- Save the flow with a clear name, such as SubmitExpenseFromApp.
- Return to Power Apps Studio and refresh the Power Automate pane if the flow is missing.
- Add a button and set its OnSelect property to SubmitExpenseFromApp.Run().
Pass named values and return named outputs
Add an input to the trigger for each value the flow needs. Give inputs stable names such as EmployeeEmail, InvoiceNumber, or ApprovalNote.
Add Respond to a Power App or flow near the end when the app needs a result. Name each output, because named outputs are easier to read and less fragile than relying on an unlabelled response.
- Open the Power Apps trigger and select Add an input.
- Choose Text, Number, Yes/No, File, or another supported input type shown by the designer.
- Use the input token in later flow actions, then add Respond to a Power App or flow.
- Add outputs such as Status, RecordID, and ErrorMessage.
- Save the flow and refresh it in Power Apps Studio.
- Pass values in the order Power Apps displays in the generated formula.
- Store the response in a variable and show the result in a label.
| Direction | Recommended pattern | Reason to avoid a shortcut |
|---|---|---|
| App to flow | Pass IDs, dates, names, and small text values | Large payloads make formulas and requests harder to manage |
| Flow to app | Return named text, number, Boolean, or ID outputs | Unstructured responses are harder to reference |
| Files | Save binary content in OneDrive or SharePoint and pass a URL or identifier | Raw attachments can create payload and connector problems |
| Collections | Use JSON.stringify in Power Apps, then Parse JSON in the flow | Very large collections should be filtered, paged, or processed in the flow |
Copyable formulas for flow inputs and outputs
Suppose the flow is named SubmitExpenseFromApp and has EmployeeEmail, Amount, and Note inputs. A button can call it with this formula: Before you commit to anything, it is worth looking at single access point unifi console.
Pass tables and collections without oversized requests
For a small collection, convert selected records to JSON and send the result through a text input. This keeps the app formula explicit and lets the flow validate the payload.
For example, a gallery containing selected expense lines can use this formula:
Store large files and pass links
Avoid passing large binary files through the response or a text parameter. Save the file in OneDrive for Business or SharePoint, then pass its path, item ID, or sharing URL to the flow. It helps to understand alternatives to power automate for sheets before going further.
A common pattern starts with the Power Apps trigger, creates the file in a SharePoint document library, and returns the item ID. Later actions use Get file content by path or Get file content by ID.
- Add a File input only when the file is small enough for your tested connector path.
- For larger files, upload from the app to a controlled OneDrive or SharePoint location.
- Pass the file name, site address, library name, and item ID to the flow.
- Use SharePoint Get file content or OneDrive for Business Get file content in the flow.
- Return the file URL or item ID, not the binary content, unless the app genuinely needs the content.
Set run-only users and connections
Run-only settings decide who can start a manually triggered flow and which connections the flow uses. They do not replace sharing the app or granting access to the underlying data.
The available labels can differ slightly between the new and classic Power Automate designer. The path below matches the standard flow details page. If that sounds like your situation, read up on automation tool for moving files on schedule next.
- Open Power Automate and select My flows.
- Select the flow, open the More commands menu, and choose Share.
- Under Run-only users, choose Add another user or group.
- Add the people or security groups who will run the flow.
- For each listed connection, choose Provided by run-only user or Use this connection.
- Choose Use this connection when the flow should use the maker's connection and the organisation allows that pattern.
- Choose Save.
- Open the flow details page again and confirm the users and connection choices are listed.
Share both the app and the flow
Sharing an app does not always give a user permission to run its connected flow. Share both resources, or add suitable co-owners who can maintain them.
Use a group when possible. A group is easier to manage than updating individual users whenever the team changes.
- In Power Apps, select Apps, open the app's More commands menu, and choose Share.
- Add users or a security group, choose the required user role, and select Share.
- In Power Automate, open My flows and choose the flow's More commands menu.
- Choose Share and add the same users or group as run-only users.
- Add co-owners only when they should edit, test, and maintain the flow.
- Ask a test user to open the app, submit a harmless record, and confirm the flow completes.
Troubleshoot failed runs and permission errors
Open Power Automate, select My flows, open the flow, and choose Run history. Select the failed run, expand the failed action, and read Inputs, Outputs, and the error code.
Compare the failed input with the value shown in Power Apps. Blank text, an invalid date, a deleted record, and an expired connection are common causes.
- Turn on a visible loading variable before .Run() and reset it after the response.
- Wrap the call in IfError where your app formula supports it, then display a useful message.
- Use a correlation ID input, such as GUID(), and write it to the flow log or target record.
- Open the matching run in Power Automate and compare its correlation ID with the app's message.
- Test the connector directly with the same connection if the flow fails before its main action.
| Message or symptom | Check next |
|---|---|
| Unauthorized or 403 | Open the failed connector action, select Fix connection, sign in again, then verify the user or maker has access to the target data |
| The requested operation is not allowed | Check the SharePoint, Dataverse, mailbox, or database permission used by the selected connection |
| InvalidTemplate | Open the failed action and inspect the expression, dynamic content type, and Parse JSON schema |
| ActionFailed | Expand the run and find the first failed action. Later failures often follow from that first error |
| Flow isn't listed in Power Apps | Confirm the environment, sharing, ownership, and saved flow trigger. Remove and add the flow again if its signature changed |
| Power Apps shows no response | Confirm every successful branch reaches Respond to a Power App or flow, then inspect the run history |
Choose a practical first workflow
An approval form is a sensible test. The app sends an employee email, amount, note, and record ID. The flow creates an approval, writes the decision to SharePoint, and returns Status and RequestId.
Invoice generation uses the same connection pattern. The app sends order data, while the flow fills a Word template, stores the document, and returns a link.
Teams, Outlook, SharePoint, and Excel can cover many internal workflows. SQL, Salesforce, HTTP, and custom connectors can introduce premium licensing or extra security work.
Start with one task and measure its real run time, failure rate, and payload size. A small test exposes permission problems before they reach the whole team.
Questions people still ask
Can a Power App trigger a flow without a button?
Yes. Call the flow from a formula such as Screen.OnVisible or a control's OnChange property. Use this carefully because each call starts a flow run and can create repeated requests.
Do app users need their own Power Automate licence?
There is no universal answer. It depends on the flow, connectors, user rights, and licensing model. Run-only settings can select the maker's connection or require a user's connection, but they do not bypass premium licensing or data permissions. Check Microsoft's current licensing pages before deployment.
Why does my flow return nothing to Power Apps?
Check that the flow contains Respond to a Power App or flow and that the successful path reaches it. Open the run history, inspect the last completed action, and refresh or re-add the flow in Power Apps after changing its outputs.
Can I send a photo or file from Power Apps to the flow?
Yes, if the tested trigger and connector support the file input. For larger files, store the binary in OneDrive or SharePoint and pass the item ID or URL. This avoids making the app response carry the file itself.
How many flows can one app call?
Use the limits published for your Power Apps and Power Automate setup rather than assuming a fixed practical number. Keep each flow focused, remove unused connections, and monitor run history and service limits.
How do I pass a Power Apps collection to a flow?
Convert a filtered collection with JSON(CollectionName, JSONFormat.Compact), pass the text to a trigger input, and use Parse JSON in the flow. For larger data, pass identifiers and process the records in the source system.