Triggers

Every pipeline starts with a trigger node. The trigger determines when and how the pipeline executes.

Webhook

The most common trigger. Creates an HTTP endpoint.

| trigger.webhook --path /api/items --method GET,POST

Accessible at: GET/POST http://host/wh/{owner}/{project}/api/items

Scheduled execution using cron syntax.

| trigger.cron --schedule "0 */6 * * *"

Runs every 6 hours.

Triggered on demand via the UI or API.

| trigger.manual

Triggers on WebSocket room events.

| trigger.ws --room my-room --event chat:message

Triggers when a key-value entry changes.

| trigger.kv.subscribe --prefix user: --durable

Exposes the pipeline as an MCP tool for AI agents.

| trigger.mcp --tool-name search_items --tool-description "Search the items collection"

Connects to an external WebSocket server.

| trigger.ws.client --url wss://example.com/feed --event message