Workflows from Apps
Workflows are automated sequences: trigger → tasks → actions. Apps can trigger and interact with workflows.
Trigger When It Fires Use Case
─────────────────── ────────────────────────────── ──────────────────────
On demand Manual or API call Testing, ad-hoc
Schedule Cron, time, or interval Daily reports
Davis problem New problem detected Alert notification
Davis event Custom event received Event-driven automation
Task Type What It Does
─────────────────── ──────────────────────────────────────
Run DQL query Query Grail data
Run JavaScript Custom logic, formatting, decisions
HTTP request Call external APIs
Send email Notify via dynatrace.email connector
Jira / Slack / Teams Create tickets, send messages
💡 Workflows need a service user as the actor — this controls whose permissions the tasks execute under. Never set the workflow owner to a service user (you'll lose access permanently).
🛠 Try it: Open Workflows → create a workflow with a "Run JavaScript" task → use fetch to call your app function's API endpoint. Now your app logic can be triggered by Davis problems, schedules, or any workflow event.