Triggers and Runs

Workflow trigger methods are configured in Workflow Settings. Drafts can be debugged before publishing; formal invocations require the workflow to be published.

Manual and API Runs

Select Run in the editor, fill in the input variables, and start. For API runs, use:

curl -X POST "$CLOUISLE_API/api/v1/workflows/<workflow_id>/run" \
  -H "Authorization: Bearer $CLOUISLE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"inputs":{"query":"检查订单状态"}}'

The inputs in the request body defaults to an empty object. The response returns a run ID; use the run query interface to get the status and result.

Webhook

1. In Workflow Settings, select Webhook.
2. After saving, a Webhook Token and URL are generated.
3. On the Access API page, copy the URL and call it with API Key Bearer authentication.
4. The request JSON directly provides the workflow input fields.

Webhook workflows must be published with the corresponding trigger enabled. The initial response contains the run ID, status, and stream_url; connecting to that URL shows node events via SSE.

curl -X POST "$CLOUISLE_API/api/v1/workflows/webhook/<webhook_token>" \
  -H "Authorization: Bearer $CLOUISLE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"检查订单状态"}'

Cron

The UI allows configuring by interval, daily, weekly, monthly, or custom Cron ("minute hour day month weekday"). Cron scheduling is not implemented yet (no corresponding Celery scheduled task in the backend; the UI only saves the configuration), so published workflows are not executed automatically on a Cron schedule. Scheduled triggers are on the Roadmap.

Status and Cancellation

Run statuses include pending, running, success, failed, cancelled, and timeout. The run drawer can cancel tasks still executing; some external API requests already sent cannot be interrupted. See the Workflow API for streaming run events.