Agentic AI › Orchestrate
Triggers
What starts a run. A trigger created from a template is never armed — a new tenant should not have agents running before anybody has read what they do.
Where to find it
- Module: Agentic AI
- Group: Build & Orchestrate
- Section: Orchestrate
- Screen: Triggers
Address in the console: /agentic/triggers
List · 10 columns · 20 fields on its form · 3 of them required
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Code | Code | code |
| Name | Text | name |
| Kind | Status | trigger_kind |
| Workflow | Text | workflow_name |
| Agent | Text | agent_name |
| Schedule | Code | cron_expr |
| Status | Status | status |
| Fired | Number | fired_count |
| Last fired | Date and time | last_fired_at |
| Next due | Date and time | next_due_at |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Code required | Text | ||
| Name required | Text | ||
| Workflow | Choice | Looked up from existing records | |
| Agent | Choice | Looked up from existing records | One or the other. A trigger that names both runs the workflow. |
| Kind required | Choice | Configuration list | |
| Schedule | Text | For a scheduled trigger: five fields as cron writes them (minute hour day month weekday), e.g. 0 7 * * 1-5 for 07:00 on weekdays. | |
| Time zone | Text | The time zone the schedule is read in, e.g. Asia/Riyadh. Empty: the company's. | |
| Event | Text | For an event trigger: the event that starts it, e.g. invoice.posted. | |
| Module | Text | For a record trigger: the module of the records watched, e.g. hrms. | |
| Resource | Text | For a record trigger: the screen whose records are watched, e.g. employees. | |
| When a record is | Choice | created, updated, deleted, status_changed | |
| Only when | Long text | A condition the record or event must meet, e.g. amount > 10000. Empty: every one. | |
| Cube | Text | For a threshold trigger: the figures it watches. | |
| Measure | Text | For a threshold trigger: the figure in that cube. | |
| Crosses | Choice | gt, gte, lt, lte, eq, neq, changes_by | gt above, gte at or above, lt below, lte at or below, eq equal, neq not equal, changes_by moves by at least the threshold. |
| Threshold | Number | The figure compared against. | |
| Never more often than (seconds) | Number | A quiet period after it fires, e.g. 3600 for at most once an hour. | |
| Most per day | Number | It stops firing for the day after this many runs. | |
| Status | Choice | inactive, active, paused, error | Only an active trigger starts runs. One made from a template starts inactive. |
| Active | Yes or no |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.