Flow List

Flow

Heartbeat represents integrations as flows. During development, define a flow by writing a flow specification with the Heartbeat SDK. After you deploy to the Heartbeat Platform or Heartbeat Agent, the flow becomes a message-processing pipeline that acts as the integration layer between systems.

To view all flows deployed for your organization, navigate to Heartbeat Console and select Flows from the left navigation menu.

The flow list appears as shown in the following image:

The Heartbeat Console displays a list of flows with action buttons for each one.

You can access a flow’s traces or view the details for a specific flow.

Headless flows do not appear in the main list, but they are still visible as "downstream flows" on the details pages of the flows that use them. Headless flows are always part of a bigger message processing pipeline, and they currently do not have their own message processing metrics.

To view headless flows directly, use the exchange type filter, as shown in the following image:

Headless flows can be viewed by selecting the exchange filter in the filter bar.

Groups

You can optionally assign a group identifier in the flow spec to group flows on this page. Select the group icon () in the top-right corner to switch to group view. The list then appears as shown in the following image:

The flow list is grouped by default, main integration, and Beatbox flows.

Flows without an assigned group are listed under "default". Flows deployed from a Beatbox installation are grouped by the name provided when creating the Beatbox ID.

Beatbox flows appear on this page only if you create an Utilihive Agent user and include its credentials in the beatbox.env file.