Triggers
Start execution from webhooks, chat, or the API
Overview
Execution can be started from three entry points. In every case, the same Think→Act→Observe engine runs: there are no pre-defined workflows—the executor decides which agents to call and in what order at runtime.
Entry points
Chat
Type a goal in natural language. The executor runs with your project's agents and mappings.
Webhook (trigger)
External systems POST to a trigger URL. Optional prompt and payload; execution is the same loop.
Schedules
Cron or recurring schedules fire at set times and invoke the executor (via trigger or chat).
Webhook triggers
Create a trigger in the UI to get a unique URL. When that URL is called (e.g. from CI/CD, monitoring, or another app), ViksaAI runs the executor with the trigger's prompt and optional payload. Results and logs are stored and viewable in the app.
Example
Trigger prompt: "Check disk on prod-db and restart the app if usage > 80%". Payload can include variables (e.g. environment, host). The executor uses the same agents and mappings as chat; no separate workflow to configure.
Schedules
Schedules are defined with a cron expression or recurrence. At the scheduled time, the Scheduler Service calls the Chat Service (or trigger endpoint). Execution is again the full Think→Act→Observe loop; outputs are stored for later review.