Event Types & Actions
import { Aside } from ‘@astrojs/starlight/components’;
Event Types and Actions are the core configuration of your automations. An Event Type names a trigger; an Action defines what executes and what happens next.
Event Types
Section titled “Event Types”Navigate to Event Types in the sidebar.
What is an Event Type?
Section titled “What is an Event Type?”An Event Type is a named definition that ties together:
- The Sink Type that will execute the task
- The Source Type that is allowed to fire it
- The Action that runs when the event dispatches
One Event Type can be triggered many times. Each trigger creates a new Event.
The Event Types Table
Section titled “The Event Types Table”
| Column | Description |
|---|---|
| Display Name | The name used when a source fires this event type |
| Action | The linked Action (module + routing) |
| Sink Type | Which kind of sink agent executes this |
| Source Type | Which kind of source is allowed to trigger this |
| Enabled | Whether this event type is active |
Search
Section titled “Search”Use the Search event types… field in the topbar to filter the table by name, action, or type. Results update as you type.
Event Type Detail
Section titled “Event Type Detail”Click the edit icon on any row to open the detail panel.
Creating an Event Type
Section titled “Creating an Event Type”Click Add Event Type and fill in:
| Field | Description |
|---|---|
| Display Name | A unique name for this event type (e.g. SEND_REPORT) |
| Sink Type | Select the Sink Type that will execute the task |
| Source Type | Select the Source Type allowed to fire this event |
| Action | Select or create the Action to run |
| Enabled | Toggle on to activate |
Parameters
Section titled “Parameters”Each Event Type can have parameters passed to the executing module. Open the Event Type and use the Parameters sub-section to manage them.
| Parameter Type | Behaviour |
|---|---|
STATIC | A fixed value defined here, always the same |
DATA | A key name — the value is read from the event payload at runtime |
SECRET | A key name — the value is read from the Secrets store at runtime |
Actions
Section titled “Actions”Navigate to Actions in the sidebar.
What is an Action?
Section titled “What is an Action?”An Action specifies:
- The module to execute (Python import path)
- What to do on success — optionally chain to another Event Type
- What to do on failure — optionally chain to another Event Type
- Additional parameters injected at runtime
Actions are reusable — the same Action can be linked to multiple Event Types.
The Actions Table
Section titled “The Actions Table”
| Column | Description |
|---|---|
| Name | Identifier for the action |
| Module | Python module path that will run |
| On Success | Event Type to trigger when the task succeeds (blank = terminal) |
| On Failure | Event Type to trigger when the task fails (blank = stop chain) |
| Enabled | Whether this action is available for use |
| Tenant | Blank = shared across tenants; otherwise tenant-scoped |
Creating an Action
Section titled “Creating an Action”Click Add Action and fill in:
| Field | Description |
|---|---|
| Name | A descriptive name |
| Module | Python import path (e.g. reports.runner) |
| On Success | (Optional) Event Type to chain on success |
| On Failure | (Optional) Event Type to chain on failure |
| Enabled | Toggle on to activate |
Action Parameters
Section titled “Action Parameters”Open an Action and use the Parameters sub-section to add parameters specific to this action. The same STATIC, DATA, and SECRET types apply as with Event Type parameters.