Triggers | Islo

The Line’s [trigger] controls how new runs start. Choose one trigger for each Line.

Type	Use
`manual`	Start a run from the CLI or API while testing or on demand
`schedule`	Run the Line on a cron schedule
`webhook`	Start a Line from an HTTP POST to its line-owned path
`integration_trigger`	Start from a GitHub, Slack, or Linear event

A schedule belongs to the Line trigger. Ask a local agent using the Islo skill to set the cron expression and timezone, validate the generated Line, and show you the schedule before deployment.

For an integration trigger, connect the provider and ask the agent to inspect its event schema and selector before it changes the Line:

islo login --tool github
islo factory triggers list --with-status
islo factory triggers get github pull_request.opened

triggers get shows the event payload and selector. Deploy the Line, send one test event, and inspect islo factory line runs <name> and islo factory trigger-events list if no run appears.

Integration triggers start Lines from provider events. Conversational @ mentions (@islo-agent on GitHub or Linear, or the Islo Slack app) go through the Delegator. See Delegations.

An incoming webhook can manage a sandbox or start one standalone execution. Use a Line webhook when the event must start a multi-stage Line. The Lines guide covers manifest validation and deployment.