Designing workflows

Learn more about how to design and create powerful cross-channel notification workflows in Knock.

The Knock workflow builder enables you to craft notification workflows that combine functions, channels, and conditional logic to determine which of your users to notify across which channels when a given event takes place in your product.

How the Knock notification engine works

As you start to dig into workflows, it's helpful to understand the basics of what happens in Knock when you trigger a workflow.

When Knock receives a workflow trigger (like the one below) for one of your workflows, it will produce a workflow run for each recipient you send in your workflow trigger.

In the example above we've included three recipients, so our workflow trigger will produce three separate workflow runs.

The workflow canvas

All Knock workflows consist of three basic parts:

  • A trigger step that starts the workflow
  • Channel steps that send notifications to your configured channels
  • Function steps that control the flow of the workflow and produce state for use in templates

The trigger step

Every workflow starts with a trigger step. When you want to run a workflow, you send a trigger call to the Knock API with an actor, a list of recipients, and a data payload with any information you want to use in the notification templates of the workflow. (More on this in triggering workflows.) When the workflow is triggered, it creates a workflow run for each of the recipients passed in the trigger call.

You won't actually need to do anything with this trigger step within the workflow builder of the Knock dashboard, but it's worth calling out that we automatically generate a sample trigger call based on the variable data you add downstream in your workflow. This way you can see all of the data you need to pass in your trigger to populate the templates of the Knock workflow.

Channel steps

A channel step sends a notification to a recipient. When the workflow engine reaches a channel step, it looks for relevant channel data on the recipient. As an example, an email channel step will look for the email property on the recipient. If no relevant channel data for that recipient is found, the step is skipped. If channel data is found, then the step will send a notification.

Each channel has a notification template (designed by you in the Knock dashboard) which inserts the data from your trigger call into a styled template for that step's given channel.

You can add any of the major channel types supported by Knock into your workflow. By default, we show all of our supported channel types, but you'll need to configure a provider with each channel before you can actually use them in a workflow. For more information on how to configure channels in your Knock account, see our integration guides.

Function steps

A function is a step in a workflow that does something to the data being passed in your trigger call. You can use functions by entering the workflow builder and adding function steps onto the canvas.

We currently support the following functions:

  • Batch (aggregate trigger calls that have the same value for a specified batch key)
  • Delay (wait an amount of time before proceeding to the next workflow step)
  • Fetch (execute an HTTP request to fetch additional data for a workflow)

Trigger conditions

Channel steps and function steps can have one or more trigger conditions that determine, at workflow execution time, if the step should be executed by evaluating a set of conditions.

Read more about trigger conditions.