Skip to main content

Flowingly Power Automate Connector

Create integrations between Flowingly and your other business systems using our Power Automate Connector

W
Written by Will Dowden
Updated over a year ago

The purpose of this connector is to provide a streamlined integration experience between Flowingly and the vast library of accessible connectors available within Power Automate.

This integration is a paid add-on available to any customer. Get in touch with your Customer Success Manager or Support@Flowingly.net if you would like to learn more about this integration.

Getting Started

Before we open Power Automate you must first ensure "Enable iPaaS Integration" has been switched on for the relevant step(s) you will be using for any integration. This can be enabled by clicking on the step of interest and navigating to the "Integration" tab.

These changes must be published before proceeding. If this is not visible within your Flowingly environment then this feature must be enabled by our Support team.

Once the "Enable iPaaS Integration" setting has been enabled you will need to navigate to the My Flows tab in Power Automate.

Add a new "Automated Cloud Flow" or "Instant Cloud Flow"

Once selected, you will be presented with a pop-up screen which you can add a name to your Flow, or alternatively skip this step and update this later.

At this point you will have an almost completely blank canvas, click on "Add a trigger" to connect to Flowingly.

Power Automate Triggers

There are currently 2 triggers available to configure your integrations, both of these have specific conditions to be met within Flowingly and will address different use cases. Therefore it is important to understand what data each one will extract from your flows to ensure the optimal option is configured for your use case.

Once a trigger has been selected you will be able to access various data points from Flowingly which have been converted into Insert tokens, which can be accessed by clicking on the lightning bolt icon when editing the parameters on any following actions in your Power Automate Flows.

When a flow step is submitted

This option should cover the vast majority of use cases and is the easier option of the two on offer to configure.

To find the flowingly Triggers, search for "Flowingly" in the search bar.

Once selected you must configure 2 parameters:

  1. The Flow Model which the data will be sent.

  2. The specific Step within the flow selected from which the data will be sent.

Note: if the Flow and/or step are not appearing in the Flow Model and Step dropdowns it is likely that you have not configured the "Enable iPaaS Integration" option on for your Flow of interest, seen earlier in the Getting Started section.

The following data points will be available to you if this trigger is selected:

  • Every individual field configured within the selected step selected

  • Flow-Identifier

  • Flow-Subject

  • Flow-PercentageComplete

  • Flow-StartedDateTime

  • Flow-StartedByUser

  • Step-Identifier

  • Step-CompletedDate

  • Step-CompletedByUser

  • Step-ReminderType

  • Step-ReminderValue

  • Step-DeadlineType

  • Step-DeadlineValue

  • Step-PlannedTimeType

  • Step-PlannedTimeValue

  • Step-PlannedCost

The above variables are now able to be used in subsequent actions within your Power Automate Flows. This can include the Start a Flow action also available within Power Automate, detailed below.

When a flow step is created

The main difference between this trigger and the previous one (When a flow step is submitted) is that Flowingly requires an action to happen before the Flow in Flowingly can proceed.

The following data points will be available to you if this trigger is selected:

  • Every individual field configured within the previous step

  • Flow-Identifier

  • Flow-Subject

  • Flow-PercentageComplete

  • Flow-StartedDateTime

  • Flow-StartedByUser

  • Step-Identifier

  • Step-CompletedDate

  • Step-CompletedByUser

  • Step-ReminderType

  • Step-ReminderValue

  • Step-DeadlineType

  • Step-DeadlineValue

  • Step-PlannedTimeType

  • Step-PlannedTimeValue

  • Step-PlannedCost

The above variables are now able to be used in subsequent actions within your Power Automate Flows.

if you have selected this option we must implement one or more of the following Flowingly actions available in Power Automate. If a Flowingly action is not configured it is likely for you to encounter a processing issues in the completed steps of the relevant flow, like the one below.

Power Automate Actions

Start a flow

When using this option there must be two Flows which have the iPaaS Integration option enabled. Those being the Flow which is our trigger step and the Flow which is the action step.

Once the trigger Flow and Step has been selected there are a few parameters which must be filled out alongside some others which are optional.

Required Fields:

  • Flow Model Name - A dropdown to select the Flow which will be started

  • Subject - Enter a subject for the Flow which will be started. This can include dynamic fields from the trigger

  • Flow Initiator - Select a user who will be assigned to this new Flow

Please note that you will have to click on the lightning bolt icon to access the insert tokens/dynamic fields noted above.

Once selected you will need to click on "See more" to find all the options available to you.

Advanced Parameters

There are also some additional parameters which can be configured although they are not required to get your integration running.

  • Assigned Actor - Select a specific user to be assigned to the first step of the new flow.

  • Users/UsersToStartFlowFor/UserToStartFlowFor - Add 1 or more user as the assignee for the first step of the flow.

  • Users/TeamsToStartFlowFor/TeamToStartFlowFor - Select 1 or more teams as the assignee for the first step of the flow.

  • Users/CcUsers/CcUser - CC in 1 or more users for oversight on the new Flow started.

  • Users/CcTeams/CcTeam - CC in 1 or more teams for oversight on the new Flow started.

Update Flow Step Fields

This action is useful for use cases where we need to access data that is not stored within Flowingly. This must be used in tandem with the "When a flow step is created" trigger as we need to use the Flow ID generated by Flowingly to configure this action.

Required Fields:

  • Flow Model - Same as the one selected in the Trigger

  • Step - Same as the one selected in the Trigger

  • Flow Identifier - This is a dynamic Insert Token that will be unique each time the flow runs.

Advanced Parameters

Once the 3 fields above have been configured you will then be presented with "Advanced parameters". This is where we will be able to use any data stored externally from Flowingly and integrate this within your Flow.

You can either select the relevant fields from the dropdown or click "Show all" to display all available options.

Depending on your use case and what has been configured previously within Power Automate, you can now determine what data needs to be entered into these parameters.

This can be done with either Insert Tokens or Inset Expressions.

Upload File to Step Fields

This action is useful for use cases where we need to access documents that are not stored within Flowingly. This must be used in tandem with the "When a flow step is created" trigger as we need to use the Flow ID generated by Flowingly to configure this action.

The other critical prerequisite for this action is that the step of interest must have a File Upload field within the form.

Required Fields:

  • Flow Model - This should be the same as the flow selected in the Trigger

  • Step - The name of the Step containing the file upload field

  • Flow Identifier - This is a dynamic Insert Token that will be unique each time the flow runs e.g. Flow-1234. Without this the PA Flow will fail.

  • Field - The name of the designated field for uploading files - this must be an exact match

  • File Name - The name you want to give to the file - this can include dynamic content from your flow or externally.

  • File Download Path - Where the file will be downloaded from, so PA can retrieve this for you.

Get in touch with your Customer Success Manager or Support@Flowingly.net if you have any use cases which cannot be addressed by the current options as we're always looking to improve!

Did this answer your question?