Workflows

Workflows in iMBrace allow you to automate processes by connecting different components, known as connectors, that perform specific actions within a sequence. Each connector represents a step in the workflow and is responsible for executing tasks such as retrieving data, processing information, calling external services, or sending messages. Once a connector completes its operation, the output it generates is passed to the next connector in the workflow. By combining connectors, users can design workflows that automate repetitive tasks, integrate systems, and respond to events without manual intervention.

Workflow Structure

Workflows are organized in a top-to-bottom hierarchical structure, where each connector represents a step in the workflow. Steps are executed in sequence, and the output generated by one connector can be used by subsequent connectors. This structure provides a clear visual representation of how the workflow operates and how data moves between steps.

The hierarchical layout makes it easier to design, review, and maintain automation processes.

Connectors

Connectors are the building blocks of a workflow. Each connector performs a specific action within the workflow, such as:

• retrieving data from a system

• applying logic or transformations

• sending messages or notifications

• calling external APIs or services

Every connector represents a step in the automation process. Once a connector finishes executing, its output becomes available to the next connector in the workflow.

Workflow Triggers

Workflows begin execution when they are triggered by an event. A trigger defines when the workflow should start running.

Common triggers include:

• incoming messages from communication channels

• scheduled time intervals

• external API requests through webhooks

Once triggered, the workflow executes the configured connectors in order, processing data and generating outputs based on the defined logic.

Workflow Engine

The workflow system in iMBrace is powered by ActivePieces, which provides the underlying framework for building and executing automation workflows. The engine manages workflow execution, connector processing, and data flow between steps, enabling scalable and reliable automation.

Autosave Behavior

Changes made while editing a workflow are automatically saved in the workflow editor. This ensures that updates to connectors, workflow structure, or configuration are preserved without requiring manual saving. Autosave helps prevent the loss of work while designing or modifying workflows.

Although workflow edits are automatically saved, certain changes only take effect after the workflow is published. For example, updates to webhook behavior or workflow logic will not affect running workflows until the updated version is published. Until publishing occurs, the previously published version continues to run.

This ensures stable execution of workflows while changes are being developed.

Version History

iMBrace maintains a version history for workflows. Each time a workflow is published, a new version is recorded. Users can review previous workflow versions and restore an earlier version if necessary. When a previous version is restored, that version becomes the active workflow used for execution.

Version history allows workflows to be updated safely while preserving the ability to revert to earlier configurations.

Workflow Automation

Using workflows, organizations can streamline operations such as automated messaging, data processing, system integrations, and event-driven responses. This reduces manual effort and ensures consistent execution of business processes.