Monitor Options

Most monitor events work by polling the application for new data, e.g. checking Twitter every 15 minutes to see if there have been new tweets since the last check. (Other monitors use webhooks so the application itself triggers the Flow to run when the event occurs).

For polling monitors, there are three options that can be chosen for when to run the Flow:

  • New Data (the default choice)
    Sets your Flow to run once for each new item. For example, if your Flow starts with a Salesforce - Monitor New event, then it will check Salesforce every 15 minutes (or whatever period of time you set it to) to see if new records have been added. If 3 new records were added since the last check, the Flow runs 3 separate times – once for each new record. If no new records were added, the Flow does not run at all.
  • No New Data
    Allows you to trigger based on no records being found that match the event and criteria you specify. For instance, you could set your Flow to check Salesforce every morning at 9am to see if there are new leads since the previous check. The “No new data” option tells the Flow to run each time there are no new leads.
  • Every Time
    Your Flow will run every time it checks the application. For instance, if you are checking every hour for new rows in a spreadsheet, the Flow will run exactly once every hour. Instead of getting data for a single row (as it does for the “New Data” option), to Flow gets a list that includes data for all of the new rows. If there were no new rows, the list is an empty list. This allows you the most flexibility to decide what actions to take, all in a single Flow. You could, for example, take different actions based on the number of rows added that hour, including what to do if there are none.

Each Flow keeps track of when it last checked the application independent from other Flows, so you can have multiple Flows looking at the same events – e.g. one that checks every 15 minutes for new items, another that runs if there are no new items during the previous 24 hours, and another that runs at the end of every week to gets all of the new items for that week.

Webhook monitors may also offer more than one option. For instance, Smartsheet - Monitor New Rows notifies the Flow as soon as a smartsheet is saved with new rows. In the default monitor setting, the Flow will runs once for each new row. But you can also opt for list mode which runs the Flow just once and passes a list of all of the new rows.

You cannot change the choice after you’ve added cards to your Flow because each choice results in different data being sent to the Flow: “New data” sends the fields of the new data, “Every time” sends a list of objects that comprise the fields of the new data, and “No new data” includes no application data at all – just the Execution ID which can be used for debugging purposes (e.g. to tell different runs of the Flow apart from each other).