Screenshot needed — orch-01: The Block library, all groups collapsed
Where: Campaigns → a campaign → Orchestration → Block libraryMust show: All five group headers — Trigger, Activity, Segment, Operators, Controls — collapsed, so the reader sees the shape of the library before any block detail.Why this shot: Nothing in the text conveys that the library is grouped, or in what order the groups appear.Placeholder — replace with the image once captured. 1440px, light theme, test data only.
Your library will not show every block on this page. Each block is enabled per setup — it appears only if the underlying service is switched on for you and the block is in your allowed set. If a block below is missing from your library, that is configuration, not a fault.
At a glance
Two things about this list are worth knowing before you read on. The communication and activity blocks are documented in their own sections, not here — a Push block behaves the same whether it sits on a canvas or in a campaign, and repeating it here is how the old documentation ended up with the same concept written five times. And Limit appears twice in the library: see Limit.
Trigger blocks
A trigger is what starts a flow. A flow needs one, and a trigger takes no input from another block.Customer event
Starts the flow when a customer does something, and keeps listening for as long as you schedule it.- Configure — pick the event under Select customer event.
- Schedule — Schedule real-time takes a start and an end date. The system starts listening on the start date and stops on the end date.
Activity event
Starts the flow from something that happened on an activity — rather than from the customer directly.- Input — connects to a Challenge, Game or Offer block. Those three are the only blocks it accepts.
- Events — which events you can pick depends on the block you connected: a Challenge offers Completed, a Game offers Won and Lost, and an Offer offers Assigned.
- Passes on — the customer plus the attributes carried by the event.
Inbound API
Starts the flow when an external system calls into Lobyco.- Passes on — the customers in the call, plus any attributes sent with them.
System event
Starts the flow from a platform-level event rather than a customer action.Activity blocks
Activity blocks are what the flow does once it has an audience. Most of them are documented in the section that owns them:- Feed, Prompt, Push, Banner and Email — see Channels, where triggering and lifecycle are documented once for every channel.
- Game, Challenge and Offer — see Activities.
Channel
Sends the flow’s result somewhere — either exported as a file, or pushed into an integrated system. The destination is chosen under Configure channel. The available types cover CSV export, promotion and audience integrations, plus several export formats each built for one named destination. Which ones you see depends on your setup.Not every channel type is offered. Two exist in the product but are deliberately hidden, and several of the CSV variants are built for one named destination each. Configure this block against what your library actually lists rather than the list in any document.
Action
Performs a platform action on the customers who reach it.Outbound API
Calls an external system with a request you define.- Configure — URL, Headers, Body type, Body, and Authentication.
- Personalization — the body accepts placeholders, so each call can carry that customer’s own values.
Segment blocks
Member segment
Selects the customers the flow acts on. The block is labelled Member segment in the library — it selects customers, and “member” here is the product’s older word for the same person.- Info and Split tabs — Info holds the definition; Split divides the result by an attribute.
- Content — shows what the segment is built from: Rule(s), or a Product.
- Reuse — a definition can be kept with Save as template and picked again later. Sync re-runs it against current data; Unlink detaches it from the saved definition so you can edit it in place.
- Passes on — customers only.
Seed
Selects customers from a file you upload, instead of from rules.- Passes on — customers only.
Operator blocks
Operators reshape the result between the segment and the activity.Enrich
Adds data columns to every customer in the result, so later blocks can use them.- Configure — add elements, each picked as a Table and a Column. The block can show you the underlying SQL query it builds.
- Passes on — customers plus the added attributes.
Split
Divides the result into groups.- Passes on — customers, plus attributes the system uses internally to track which group each one landed in.
Combine
Merges two inputs into one result.- Passes on — customers only.
Intersect
Keeps only the customers who appear in both inputs. Its input port is labelled Intersect input.- Passes on — customers only.
Exclude
Removes one input’s customers from the other’s.- Inputs — the two ports are labelled Include input 1 and Exclude input 2. The result is everyone in input 1 who is not in input 2. The order matters, and the labels are the only thing on screen telling you which is which.
- Each port takes more than one input. The block is built for it, and says so: “This block is intended to operate with two or more inputs per port. Using zero or one may lead to incomplete or unintended results.” That warning only appears when a port has nothing connected, so one input per side gives you no warning — read the message as guidance on what the block is for, not as a check that will catch a thin setup.
- How each port combines its inputs is configurable — under Configure operation, a port can either combine its inputs or intersect them. Both ports default to combining.
- Passes on — customers only.
Collateral assign
Hands out collateral to the customers reaching it, with caps so no one receives too much.- Configure — Collaterals to hand out, and the limits: Max collaterals per member, Max collateral activations, Deduplication days, and Single row per member.
- Review — the configurator shows Delivered counts against the assigned collateral.
Personal offers
Assigns personal offers to the customers reaching it.Control blocks
Delay
Holds each customer at this step for a set time, then lets them continue. The block is called Delay; Wait for is the field inside it.- Configure — Wait for a number and a unit, and optionally a time of day to continue at.
- Behaviour — in the product’s words: “Each customer waits [value] [unit] from the moment they reach this block and then continues.” The clock starts per customer, when that customer arrives — not when the flow starts.
Limit
Caps how many customers pass this step. In the product’s words: “At this step, stop allocating customers once any of these limits is reached”. You can add more than one limit, and the block stops allocating as soon as any of them is reached. Four kinds are available:
The block summarises itself in plain language once configured — for a total, “At most 500 customers in total may pass this step.”
What can connect to what
A link is only useful if the next block can read what the previous one hands over. The blocks that build an audience pass on one of three things:
The practical consequence: if a later block needs an attribute, an Enrich block — or a trigger that carries attributes — has to come before it. A chain that runs Member segment → Combine → Exclude carries customers and nothing else.
Blocks not yet described
These blocks are in the library, but this page does not yet describe what they do in enough detail to work from. They were left out rather than guessed at, and need confirming with the product team:- System event — which platform events are available, and what each one carries.
- Action — which platform actions it can perform.
- Personal offers — how offers are chosen and what limits apply.
- Channel — the full list of channel types, and which are intended for general use.
- Split — how the split is configured and how groups are sized.
Related
- Orchestration canvas — adding and connecting these blocks
- Find and manage campaigns — finding a campaign and reading its runs
- Schedule and run a campaign — setting when it runs
- Campaigns — how a journey fits together