Workflow¶
The Workflow page provides a visual canvas editor for configuring event-driven automation and process flows. Workflows define what happens when specific platform events occur — such as automatically issuing certificates when a registration is approved, or sending notifications when an event goes live.
Workflow Overview¶
Workflows connect triggers (platform events) to actions (automated responses) through a drag-and-drop canvas. Each workflow is a directed graph of nodes and connections that execute sequentially or in parallel when triggered.
graph LR
T[Trigger: Registration Approved] --> A1[Action: Issue Certificate]
A1 --> A2[Action: Generate Data Package]
A2 --> A3[Action: Send Email Notification] Workflow List¶
The workflow list displays all configured workflows.
| Column | Description |
|---|---|
| Name | Workflow display name |
| Trigger | The event that starts the workflow |
| Status | Active, Inactive, or Draft |
| Last Run | Timestamp of the most recent execution |
| Run Count | Total number of times the workflow has executed |
| Event | Associated event (if scoped to a specific event) |
Workflow Canvas¶
Click a workflow entry to open the canvas editor, or click Create Workflow to start a new one.
Canvas Controls¶
| Control | Description |
|---|---|
| Zoom | Scroll wheel or pinch to zoom in/out |
| Pan | Click and drag on empty canvas to pan |
| Select | Click a node to select it and view its properties |
| Connect | Drag from a node's output port to another node's input port |
| Delete | Select a node or connection and press Delete |
Node Types¶
Triggers¶
Trigger nodes define what starts the workflow. Each workflow has exactly one trigger.
| Trigger | Description |
|---|---|
| Registration Approved | Fires when a player registration is approved |
| Event Status Changed | Fires when an event transitions status (draft → active → completed) |
| Node Captured | Fires when a MAGK Node is captured during gameplay |
| Score Updated | Fires when a team's score changes |
| User Created | Fires when a new user account is created |
| Scheduled | Fires on a cron schedule |
Actions¶
Action nodes perform operations when the workflow executes.
| Action | Description |
|---|---|
| Issue Certificate | Generate a TAK client certificate for a player |
| Generate Data Package | Create a data package with certificates and server config |
| Send Email | Send an email notification using a template |
| Send Notification | Push an in-platform notification |
| Update Record | Modify a database record (event, registration, user) |
| HTTP Request | Make an outbound HTTP request to an external service |
| Delay | Wait a specified duration before continuing |
Conditions¶
Condition nodes branch the workflow based on data.
| Condition | Description |
|---|---|
| If/Else | Branch based on a field value comparison |
| Switch | Branch to multiple paths based on a field value |
| Filter | Continue only if the data matches a filter expression |
Node Configuration¶
Click a node to open its configuration panel on the right side of the canvas.
Each node type has specific configuration fields. For example, the Send Email action:
| Field | Type | Description |
|---|---|---|
| Template | Select | Email template to use |
| Recipient | Expression | Email address (supports variables like {{player.email}}) |
| Subject | Text | Email subject line (supports variables) |
Variables¶
Workflow variables carry data between nodes. The trigger node provides initial variables based on the event type, and each action node can add or transform variables for downstream nodes.
Use {{variable.path}} syntax to reference variables in node configuration fields.
Workflow Execution¶
Activating a Workflow¶
Set a workflow's status to Active to enable it. Only active workflows execute when their trigger fires.
Execution History¶
View past executions from the workflow detail view under the History tab.
| Column | Description |
|---|---|
| Run ID | Unique execution identifier |
| Started | Execution start timestamp |
| Duration | Total execution time |
| Status | Completed, Failed, or Running |
| Trigger Data | Summary of the data that triggered the run |
Click a run to view the step-by-step execution log, including which nodes executed, their inputs/outputs, and any errors.
Related Pages¶
- Registrations — Registration approval triggers
- Certificates — Certificate issuance actions
- Data Packages — Data package generation actions
- Events — Event status change triggers
- Settings — Email and notification configuration