FME Flow: 2026.1
Automation Apps
Select Flow Apps > Automation Apps tab.
Automation apps allow authorized FME Flow users to run Automations that originate from a Manual Trigger as "apps" from a web browser. The apps are shared as URLs, and may be presented through customizable web pages.
The Automation Apps tab of the Flow Apps page lists the automation apps that have been created.
By default, all apps are enabled to run when created. Disabled apps do not run. To disable or enable an app, select an app, then select Actions > Disable or Enable.
From the Actions menu, you can also Remove an app or Change Expiration of an app.
To view and run an app, or copy an app's URL, click the View or URL icon of the corresponding app, respectively.
To edit an automation app, click on it.
To Create an Automation App
- Click Create under the Automation Apps tab. Alternatively, to duplicate an existing automation app and revise, select an app, and select Actions > Duplicate. The Create Automation (or Duplicating) App dialog opens. Complete or update the following:
- Name: Provide a name for the app. The name appears on the run page for the app. App names are case-insensitive.
- Title (optional): Provide a title for the app. The title appears in place of Name on the run page for the app.
- Description (optional): Provide a description for the app. The description appears on the run page for the app. Use the toolbar widgets to customize the appearance of the description, as desired.
- Automation: The automation you want the app to run. You can only select an automation that initiates with a manual trigger.
- Allowed Users: Access to the app is restricted to the specified FME Flow Users.
- Allowed Roles: Access to the app is restricted to users who belong to the specified Roles.
- Parameters: If the manual trigger of the automation outputs Manual Parameters, configure the default values for each one when the app runs.
- Show in App: If checked, the app allows the user to explicitly specify a value for the parameter, or accept the default value. If unchecked, the app page does not display the parameter, and the app runs according to its default value.
- Resource Permissions: If the designated Automation requires access to additional Resources, click Add Resources to specify the Resources folder that app users have permission to access. In the Select file for dialog, click the plus (+) icon beside each Resources folder to add. When finished, click Confirm.
- Connection Permissions: If the designated Automation requires access to additional Database Connections or Web Connections, click Add Connections to specify the connections that app users have permission to access. In the Add Connections dialog, click the plus (+) icon beside each connection to add. When finished, click Add Connections.
- Customize (optional): You can customize various elements of the run page for the app. Alternatively, to specify that the app should run as soon as its URL is invoked, without displaying a run page, enable Run Immediately (at bottom).
- Browser Icon: A clickable icon to reference the app URL.
- Heading Background Color: A background color to comprise the banner at the top of the app page. Appears behind Heading Banner, if transparent.
- Heading Logo: Appears over Heading Banner and/or Heading Background Color, centered.
- Heading Banner: An image to comprise the banner at the top of the app page. If transparent, appears over Heading Background Color.
- Footer Text: Appears beneath the Links on the app page. Use the toolbar to customize as desired.
- Footer Logo: Appears beneath Footer Text, and behind Footer Banner, if transparent.
- Footer Banner: An image to comprise the banner at the bottom of the app page. If transparent, appears over Footer Logo.
- Click Create. A message appears to indicate the app is created, along with the app URL. Click Copy to copy the URL. To run the app, click the URL.
- Click Close. The Flow Apps page re-opens and lists your new app on the Automations Apps tab.
To revert to the original default values of the trigger, click Reset.
Note Other permissions may still be required, and you may need to further test and adjust the given permissions. For more information about permissions in FME Flow, see Role-Based and User-Based Access Control.