The Virtual Environment

You do not sign into the canvas separately. En Garde signs you in for you, using a session that names three things: the tenant, the workspace, and the brand you currently have selected. That context is what makes the environment scoped — a flow you build while one Brand Space is selected belongs to that context rather than to your login generally. The session is short-lived and refreshed automatically while you work, so a long editing session does not drop you out.

Switching Brand Space switches the canvas context too. If you manage several brands or clients, confirm which one is selected in the header before you start building — that is the single most common source of a flow ending up on the wrong brand.

A workflow is a graph. Each node does one thing, and each edge passes the result of one node into the next. In practice the nodes in a marketing workflow fall into a few roles:

• An input or trigger — what starts the run and what it starts with.
• Conditions — checks against audience or campaign state that decide whether and how the flow continues.
• Work — the model calls and transformations that generate or evaluate something.
• Actions — writing back out, such as syncing a profile to a connected tool or producing a content asset for review.

Flows are saved with a name, a description, and the node and edge count, and appear in your agent list once saved. Building and editing happens on the canvas itself — the surrounding En Garde screens list, trigger, configure, and monitor flows rather than editing their contents.

An empty canvas is rarely the fastest start. Workflow Templates lists pre-built automations you can search by name or description, each showing its category, how many steps it has, and how often it has been used. Choosing Use Template opens the builder pre-populated with that template, ready to adapt. The agent gallery is the other source: browse shared agents by category, sort by popular, top rated, newest, or most cloned, and clone one into your own brand.

A flow can be exercised three ways, and they are worth using in this order:

1. Run it on the canvas with a sample input while you are still building, so you can see the output of each step before anything reaches a live tool.
2. Trigger it from My Agents. Each agent card has a Trigger Agent button that starts a run on demand — the safest way to confirm the deployed version behaves like the one you tested.
3. Let it fire itself once you trust it, on a schedule or from a configured trigger.

Configure on an agent card opens its configuration screen, which has four tabs:

• Configuration — the agent's own settings, presented as a form. Some agents need none, in which case the tab says so.
• API Keys — credentials the agent needs, each showing its name, a key prefix, when it was last validated, and whether it is currently valid.
• Schedule — whether the agent runs on a schedule, and whether that schedule is enabled or disabled.
• Triggers — the events that start it.

Two screens answer most questions. Activity is the real-time log of workflow executions and events, newest first, each with a status. The Executions monitor covers runs in more detail: status (pending, running, paused, completed, failed, or cancelled), progress, how many steps completed, failed, or were skipped, start and end time, total duration, and the error message when there is one. Start with Activity to find the run, then open the execution to see which step failed.