Microsoft Flow Architecture: Triggers and Actions

Published July 23 2019 by Ori Fishler
Back to insights


In the first part of this blog series on Microsoft Flow, we provided an overview on high level architecture details. Now let’s get into some of the details regarding Triggers and Actions.

Microsoft Dynamics 365 Flow - Triggers and Actions


Triggers define what gets the Flow running


Microsoft Dynamics 365 Triggers_Scheduled

Event Driven:

Microsoft Dynamics 365 Flow_Triggers and Actions_ Triggers_Event Driven_Item created

Called from PowerApps

Microsoft Dynamics 365 Flow_Triggers_PowerApps

Flow Button (triggered from App)

Microsoft Dynamics 365 Flow Button_triggered from app    Microsoft Dynamics 365 Flow_Shareing Buttons

Selected SharePoint item or Document, shown in Flow menu

Microsoft Dynamics 365 Flow_Manual Trigger WFTest_flow menu interface

Microsoft Dynamics 365 Flow_ Run Flow_ request approval



Microsoft Dynamics 365 Flow_ selected sharepoint item or document, shown in flow menu



Actions allow the flow to interact with other systems using Connectors. Standard connectors come with a standard O365 subscription. Premium connectors are available from many vendors and may require some additional cost.

You can also create Custom Connectors.Microsoft Dynamics 365 low_ Actions_new trigger

  • Describe REST interface using Postman or OpenAPI
  • Can provides Actions and Triggers
  • Can be implemented as Azure Functions

Action Properties:

  • Action has a default “name” which can be changed with “Rename”
  • Add a comment – Add a user defined comment
  • Settings – Adjust some advanced settings
  • Configure Run After
  • Peek at the underlying logic apps code
  • Delete the action
  • View/add connections used by the action 




Microsft Dynamics 365 Flow_ sending email_ actions

Action Name:

  • The action name should describe what the action is doing from a business perspective.
  • The name is used as the name of the result object returned by the action (JSON) so it is important to set this early before the action results are used.
  • Once the actions results are referenced by dynamic content the “rename” option will be disabled and the name cannot be changed

Microsoft Dynamics 365_Flow_Action Name_


  • Set advanced properties for an action. Some actions may have different properties available
  • Timeout – can set timeout on asynchronous actions (i.e. Approval)
  • Adjust retry policy

         Microsoft Dynamics 365_Flow_exponential interval_fixed interval

  • Tracked properties

o   Add property to Action JSON object results



Configure “Run After”

  • Used to handle errors and timeouts by actions
  • This will be covered more in error handling section


Ori_Flow_blog image 15



View / Add connection used by the Action:

  • Shows connections used by the action and allows adding new connections
  • Connections for the entire flow are shown in the portal (Flow->Details->Connection Section “See All” link). Covered more in Security section.


Ori_Flow_blog image 12

Looking to learn more about Office 365 in the cloud? Watch this on-demand webcast to learn all about the modern O365 environment. Discover what’s new with SharePoint, Teams, PowerApps, Microsoft Flow and how to migrate your traditional SharePoint and Apps to the modern environment, as well as other best practices from our team’s experiences to help you get the most out of Office 365.



Ori is a visionary and goal oriented senior business and technology executive who has demonstrated ability in impacting business environments. He holds several years of experience in planning, designing and implementing successful technology solutions that drive business results.

Contact us