TABLE OF CONTENTS

• Connections
  • Creating a New Connection
  • Viewing and Managing Connections
• Runs

The Workflows page includes two tabs: Connections and Runs. These tabs allow monitoring and managing your project's connections to external systems and flow execution history.

Connections

The Connections tab allows users to manage and view integrations between the current project and external systems.

Connections are typically a one-time setup per application. Once configured, they enable your flows to communicate with external systems using the stored authentication details (for example, app keys or tokens).

Creating a New Connection

To create a new connection:

1. Navigate to the Connections tab.
2. Click New Connection.
   
3. Select the system you want to connect to.
4. Specify the Connection Name.  
5. Enter additional configuration details depending on the target application.
6. Click Save.
    

Note: When connecting to CafeX applications, the connection details are pre-configured automatically. A default connection is created and used by your flows. 

Viewing and Managing Connections

Connections are displayed in the table with the following columns:

For each connection, the following actions are available:

• Rename the connection ().
• Reconnect ().

You can also narrow down the list of existing connections using the following filters:

• Status – Filter by connection state (Active, Missing, Error).
• Pieces – Filter by the app connected.
• Display Name – Search by the user-defined name of the connection.
• Owner – Filter by the user who created or owns the connection.

Runs

The Runs tab provides a history of workflow executions.

Runs are displayed in the table with the following columns:

You can narrow down the list of runs using the following filters:

• Flow Name – Filter by the name of the workflow.
• Status – Filter by execution status (Failed, Quota Exceeded, Internal Error, Paused, Running, Succeeded, Memory Limit Exceeded, Timeout).
• Date Range – Select a start and end date to view runs within a specific timeframe.

For failed or incomplete executions, a Retry button becomes active to attempt re-running the flow.