Triggers
Run agents in response to provider events — and fire governed actions back, automatically.
A trigger runs work when something happens at a provider — a new GitHub star, a new Gmail message, a new Slack message. Each firing records a typed event, and — as the differentiator — a trigger can fire a governed action in response, so the reaction passes through the same policy, approval, and audit controls as any other action.
How a trigger fires
- Webhook delivery — for providers that push events, the inbound webhook is matched to your active triggers (by event type and your config filters) and recorded.
- Polling delivery — for providers that don't push, Nolixan polls the provider on a cadence, diffs against a stored cursor, and emits an event per new item. The first poll establishes a baseline (it never floods you with history).
Either way, the firing is deduplicated and stored as a trigger event you can inspect.
The catalog
Each provider declares its available trigger types — name, payload schema, and whether it's delivered by webhook or polling:
Trigger types are named provider__trigger (e.g. github__new-star), the same convention
as actions.
Firing a governed action
A trigger can carry a target action. When it fires, Nolixan runs that action through the
governed execute path — so a write can be denied by policy, held for
approval (by a different person), and is always
audited. The event records the outcome (action_fired,
action_approval, action_denied, or action_failed).