Event Triggers

As previously discussed event triggers are listeners. They are the things that kick off a flow.

Some of the more dynamic and useful triggers are:

• Request

• Email

• Schedule

• When document is created

Request

The triggers within the Request connector is my favorite. This trigger sets up a listening URL and accepts requests just like any other API. During the setup process a json schema is defined and all of the actions leverage data passed in through the API call. More on this connector later.

Email

The Office 365 Outlook triggers can start for a variety of reasons. Some are going to be more useful than others. One of the more useful things to do is to start the flow as soon as a new email arrives.

Schedule

Much like it sounds the Schedule trigger will run based off a pre-defined time. In the example below the trigger fires every 5 minutes. The trigger is fairly simple to setup. The only required fields are to define the interval and frequency. Within the advanced options start time and time zone can filled in.

When a Document is Created

This trigger exists for both OneDrive and for SharePoint. The trigger for OneDrive needs only a folder name.

The trigger for SharePoint needs a little more detail, but not much. This trigger needs a SharePoint site and the folder to monitor.

I feel its pertinent to add you can only access SharePoint sites and folders that you (or the account being leveraged) has access to.

Others

Other connectors you may find to have useful triggers:

• Twitter - When a tweet is posted

• RSS - When a feed is published

• Gmail - When a new email arrives

• DropBox - When a file is created

• FTP - When a file is created

• Instagram - When new media is uploaded

• Google Contacts - When a contact is modified

• SQL - When an items is created

• and many, many, many more