Automations, schedules, and triggers
Use Automations in hosted Gideon to start useful work on a schedule or after a relevant event. In a self-hosted console, this surface is called Triggers.
Make the task work once
Run a small example manually before making it recur. Confirm the sources, required connections, output, and review step. An automation repeats the brief you gave it, including any ambiguity.
Set a schedule
Specify the cadence, time, and timezone. Ask Gideon to confirm the next intended run and where the result will appear before relying on it.
Prepare a weekly brief every Monday at 09:00 Europe/Berlin using [sources]. Include changes since the last brief and links to evidence. Save the result for review; do not send it externally. Confirm the schedule and how to pause it.
Use an event trigger
A trigger responds to a supported event, such as a matching memory update. Define exactly what should cause it to fire and how often. A one-time alert should have a bounded firing condition rather than recur indefinitely.
Review runs and delivery
Inspect run history and the generated result. Silent jobs can suppress automatic delivery, so an absent notification does not alone prove a job failed. Conversely, a scheduled job existing does not prove its latest run succeeded.
Pause or remove a routine
Disable the automation when the need ends or its connection changes. Check for already-running work separately. Review its destination before enabling external delivery.