Overview

Triggers can be used to specify conditions under which a flow is automatically run.

Types of triggers

1. →

   The presence of a manual trigger allows a flow to be run on-demand by authorized HASH users.

2. →

   A continuous trigger monitors data or events, and starts a flow when some predefined criteria is met.

3. →

   A schedule trigger starts a flow at a particular future point in time. This can be either a specific point in time, or a recurring/periodic basis.

Example use cases

Using manual triggers

On a one-off, or as-needed basis...

1. →

   Perform chains of related actions with just one-click (allowing multi-step actions to be compressed into reliable, automated flows)

2. →

   Generate reports for stakeholders upon request (servicing requests more quickly and dependably)

Using continuous triggers

Monitor and respond to...

1. →

   External events. e.g. monitor a competitor's blog's RSS feed, and generate a summary for internal consumption when a new post appears, and post to Slack.

2. →

   External data. e.g. when some metric in an external application crosses a specific threshold, send an email and SMS alert to the responsible stakeholder.

3. →

   HASH events. e.g. when one flow successfully finishes running, start another one in follow-up.

4. →

   HASH data. e.g. when an email address appears as an attribute on an entity in a web, run a reverse-lookup to identify the social media accounts associated with it.

Using schedule triggers

1. →

   Fixed point in time: e.g. run on 2030-01-01 at 12:00PM PST

2. →

   Recurring: e.g. every Friday at 09:00AM EST