This article is part of the Getting Started: Integrations help series.
Before diving deeper into the integration process itself, it is useful to introduce a few Bosbec-specific concepts. These form the foundation of how integrations are built and executed within the platform.
Understanding these concepts will make it easier to reason about how data flows from System A, through Bosbec, and onward to System B.
Triggers
Triggers are the starting points of any workflow and are required for the Workflow Engine to run.
A trigger defines when a workflow should start. When the configured conditions are met, such as an incoming request on a channel or a scheduled event, the workflow starts and the connected jobs are executed sequentially.
In practice, triggers often represent events originating from System A, such as:
- An incoming webhook
- A scheduled import
- A manual or test execution
Units
The primary data storage concept in Bosbec is the Unit.
Units can be modeled to represent virtually anything relevant to an integration, for example:
- A person, with a name and contact details
- An order, identified by an order ID and purchase information
- A parking space, with status and license plate number
You decide what a unit represents based on the needs of the integration between System A and System B.
Data is stored on units using metadata. Metadata is a key-value system in which you define a key (e.g., order_id) and assign it a value (e.g., 123456). These values can then be referenced, updated, and used throughout your workflows.
More information on working with variables and metadata can be found here.
Channels
Channels are the entry points into the Bosbec platform. They define how traffic enters Bosbec and routes it to triggers within workflows.
A channel represents the technical interface through which System A communicates, such as an HTTP endpoint or email address, while triggers determine whether the workflow should start.
Later in this guide, we will go deeper into how channels and triggers work together, but you can also read more about channel setup here.
Interactive mode
When a workflow is running, it can be opened in interactive mode.
Interactive mode allows you to:
- Follow the exact execution path the workflow has taken using the timeline.
- Inspect what each job has done and which decisions were made.
- Move the debug pointer to debug or rerun individual parts of the flow.
This is especially useful when building new workflows or troubleshooting integrations between System A and System B, as it provides full visibility into how data is processed step by step.