Skip to main content

Triggers & automations

Admin

Unattended runs are configured under Settings → Capabilities, on two tabs: Agent Triggers (fire one agent on an event or schedule) and Automations (multi-step pre-configured actions).

Looking for the full trigger guide?

This page covers the admin settings surface. For the end-to-end walkthrough (building scheduled and event-based triggers on an agent, webhook sources, run history, and limits), see Agent triggers.

Agent Triggers​

Capabilities → Agent Triggers (/settings/capabilities/agent-triggers) lists every trigger in the org with its Name, Source, Status, and Last updated. Click + Create a trigger to add one.

Agent Triggers tab listing webhook triggers with status
Agent Triggers: one row per trigger, with source icon and Active status.

Automations​

Capabilities → Automations (/settings/capabilities/automations) is for multi-step flows: "Automations let you run pre-configured actions automatically when specific events happen in Ask." Click + Add automation to create one.

Automations tab with empty state and Add a new automation button
The Automations tab (empty state).

Which one do I want?​

  • Agent Trigger: the unit of work is "run this agent with this input", e.g. a webhook from GitLab kicks off a review agent.
  • Automation: the work is a sequence of steps or coordinates several agents, e.g. every weekday at 08:00, summarize yesterday's tickets and post the result to a channel.
Who can manage these

The Manage triggers permission (see Roles & permissions) gates both tabs.

AgentsAgent triggersThe end-to-end guide: schedules, events, webhooks, run history.AgentsCreate your first agentYou need a published agent before you can trigger it.AdminAdmin console overviewThe full map of the redesigned Settings.