Flows

Flows provide powerful ways to engage with your users. Flow editor is highly intutive way to way to organize all the LivePinch components in any way of your choosing to engage your users. Following sections describe in detail, how you can use flows to prepare live interactive engagement for your users.

Creating a Flow

As with all other channels, each flow requires a name. You can create a new flow by clicking on New Flow button and fill in a label. The label needs to unique, to differentiate one flow from another. We recommend choosing a name that is a concise idea behind the flow.

Below screen shows the “New Flow” screen

../_images/flow-new.png

Editing a Flow

Once a flow is created, you are taken to edit screen. The edit screen is shown below.

../_images/flow-blank-edit.png

Flow Edit Pane

This is primary editing area for your flows. As you drag and drop component, Each component you drop has one or more events you can use to connect to subsequent components. As an example, If you drop an Email block, events associated would be sent, opened, bounced, clicked, unsubscribed etc. The subsequent connections are optional.

Also, each component, has an edit icon within the compoenet, you can use this to setup the content or settings for that specific component.

In case of Email block, you will need to setup the content withing the email. The email, editor and their settings are discussed at length in Email section

In case of Wait block, you will need to set up how long the wait duration must be. Each of these components are discussed in deail in following sections.

As you edit, remember following rules about validity of a given flow.

  • Flow must always start with a trigger node. Trigger nodes are Profile List, Segment or an Event, This rule is obvious, for example, you can not start a flow with Wait component, or an Email compoenent
  • All components must have at least one incoming connection. You can not have isolated components
  • No connection can contain a cycle. Cycle happens when outgoing event of a component, say Email Sent, is connected back to an earlier component that is feeding into this component. For example of this, if you have a Wait Node that sends an email at the end of wait period, the Email block can not set one of its events back into earlier wait component
  • All components must be setup correctly with content before you publish a flow

Outside these rules everything is fair game.

Flow Components

LivePinch currently supports following trigger nodes

  • Profile List - This is entire list of profiles, you can choose subset of these profiles, such as iOS Users, Android Users etc, you can do this
  • Segment - Any rule based segment or segment exported from reports can be chosen as starting point of a flow
  • Event - If you’ve integrated SDK’s and are receiving events from SDK, you can use any incoming events, with optional filters as starting point for a flow

Following Action Nodes are supported

  • Send Email
  • Send SMS
  • Send Android Push
  • Send iOS Push
  • Send Web Push
  • Set User Attributes
  • Send Survey
  • Make an HTTP request

Following Conditional components are supported

  • Wait ( Wait for a fixed duration before proceeding )
  • Wait for Event ( Wait for fixed amount of time for an event to arrive )
  • Wait for Date ( Wait for a set date before proceeding )
  • Check Condition ( Check if user matches a certain condition )

Finally, you can signal an end of flow by using the End Component

Flow Settings

Flow settings are required to be set if you use either Email, or SMS within a flow, you’ll need to choose ESP Provider or SMS provider to use for sending out emails/sms from within this flows. If this is unset, you can proceed to publishing a flow.

Publishing a Flow

When you first hit publish, if you have no errors within the flows you will be prompted for a schedule for the flow. The errors if any are in any of following three categories

  1. Structural Errors - This happens there’s violation with following Flow Rules
  2. Content Errors - This happens if any of the components are correctly setup with content
  3. Setting Errors - This happens if you havent updated settings, ie. ESP/SMS Provider

If you’re clear of these errors, you can schedule your flow as onetime or recurring. Recurring schedules are only applicable to flows starting with either Profile List or Segment. Please see Schedule section for an in depth discussion on recurring sendouts.

../_images/flow-publish.png

Stopping a Flow

You can stop a currently activated flow by clicking on Published button at the top right, and confirming the Stop action in the right pane

Copying a Flow

Once stopped, a flow can not be rescheduled to start again. You however can clone a flow from the listing section. Make any edits, and publish the newly created flow.