Create an automation trigger
Create a schedule (cron) or event trigger. Schedule triggers require
a valid cronExpression; event triggers require an eventType. The
run acts as runAsUserId (defaults to the caller); binding another user
requires internal-operator privileges (privilege-escalation guard).
Consequential — writes an audit entry.
Authorizations
API key or personal access token (NEX-1042). Send as
Authorization: Bearer <token>. Token format:
nex_live_…— live API key (server-to-server)nex_test_…— sandbox API keynex_pat_…— personal access token (acts as the issuing user)
Authorization is decided by the key's scopes array, not the
owning user's RBAC role. See POST /api/api-keys to mint a key.
Path Parameters
Body
Create/update payload for an automation trigger.
schedule, event, manual, webhook Required + validated for schedule triggers.
Required for event triggers.
Defaults to the caller; binding another user needs internal-operator rights.
Response
Trigger created
An automation trigger that fires an agent on a schedule or event.
schedule, event, manual, webhook 5-field cron; required for schedule triggers.
IANA timezone for cron evaluation (defaults to UTC).
Business event name; required for event triggers (e.g. shift.ncns).
Equality filters (dot-path) the event payload must satisfy.
Identity the run acts as (drives tool scope + RBAC).
Auto-disabled after 5 consecutive schedule-dispatch failures.

