Flows

CustomerOS Flows consist of Flow Actions, which are used as units of automation and for billing. Flow Actions take an input, carry out an action and then output data.

Think of them as 3 components:

1. Triggers
2. Actions
3. Outputs

Flows can also include waits, which do not count as Flow Actions for billing purposes, but allow you to set delays to create campaigns.

Conditional logic is also possible through If/Then blocks.

​

How should I use Flows?

Any time a repetitive action should be taken a Flow can be used. For instance, a flow can be triggered every time a person is added to CustomerOS to find and add their work email address to that contact.

​

Setting up your first Flow

For your first flow you should choose what should trigger the flow. For testing, you can choose a manually added record that allows you to trigger a flow whenever you want by adding the object (person, organization) directly to the flow to start the flow.

You can chain multiple actions within a flow, however for simple first flow, just choose an easily observable event, like sending an email or LinkedIn message.

In the case of automating an email send to a person, the

1. Trigger = Person added to Flow manually
2. Action = Send Email
3. Output = Send data to Mailbox to send email