# Schedules & automations Turn a useful workflow into work that runs at the right time or in response to an event. Source: https://docs.opser.com/agents/automations/ ## Start with a working task The simplest way to set one up is to ask the agent in its chat. Say what should happen and when: the agent uses your workspace context, asks about anything unclear, and creates the automation. Agree on the task, source records, destination, and timezone before it does. On an agent other people use, everyone with access sees, sets up and changes its automations, unless its owner turned that off; then only its owner or an admin does, and the results still appear in the agent's chat. > Every Monday at 9 a.m. in my timezone, summarize overdue tasks by owner and send me a short update. Do not change task statuses. You can also ask for the task once in the chat first. Check the saved schedule rather than assuming that “tomorrow morning” means the same time to everyone. ## Schedules and event triggers To set one up yourself, open the gear in the chat's header, choose **Automations**, then **New automation**, under the section's description. Give it a title, write the task in **What should this automation do?**, and choose **Add trigger**: **Automations · Fictional data** A briefing runs Mondays at 09:00 Europe/Rome. A second automation responds to a customer-request app event. Both are enabled. - **On a schedule:** repeats hourly, daily, weekly, or monthly at the time you pick, in your timezone. - **Once:** runs one time, at the date and time you pick. - **When something happens:** runs on an app event. Choose an installed Opser app or a connected account, then one of its events. Opser app events need no connected account. The agent receives the event details when it runs. Choose **Create** to save it; close the form to drop it. If nothing can start an automation, **App** shows **No apps installed**; an app without exported events shows **No events available**. Available apps and events depend on the workspace and the agent's access. The agent can discover these same app events, and the events of its connected accounts such as a new email in Gmail, when you ask for an automation in the chat. ## Review ongoing work New automations, whether you create them or the agent does, run automatically by default. Creating one pre-approves the actions described in its task, including sending emails and updating app data. There is no separate app-access checklist or per-action approval prompt during those runs. Be precise about the intended actions and recipients. Automatic execution still requires valid app permissions, connected accounts, and available usage credits. It does not grant new access. Older automations retain their original execution restrictions. A schedule without valid authorization pauses with **Needs authorization** instead of repeatedly failing or losing its saved task. Each run works on its own, and its results show in the agent's chat; they reach the agent with the next message in the chat. Every run lists in the **History** tab, beside the automations. Check the first one there: **View** opens the chat at that run's latest message, and a run waiting on you shows **Review**, with the approval above the composer. Inspect the result before relying on it. If required access is missing, fix that access rather than repeatedly retrying the task. When weekly-review email delivery is enabled for your workspace, a successful default weekly-review run can also send a report to the default agent’s owner. Delivery depends on the available evidence, email preferences, and frequency limits. A failed run does not send its report. Review the result in the chat and manage optional emails in **Settings → Notifications**. For a failed scheduled run, ask the agent to inspect its diagnostics without rerunning it. The agent can show recorded errors, attempts and tool operations that you are allowed to see in the chat. An attempted action does not confirm a saved change; check the affected records before retrying. Recorded detail can be incomplete, especially for older runs or worker interruptions. ## Pause, edit, or remove Use the automation controls to pause, change, or remove work you no longer need. You can also ask the agent in chat to adjust an existing automation: it updates the schedule, task, timezone, or event source in place, so the automation keeps its identity and run history instead of being deleted and recreated. If the automation changed in the meantime or a run is in progress, the edit is rejected rather than applied blindly. Changing an automation someone else set up makes it yours: it runs with your access from then on. Each automation lists its trigger with a distinct icon and label, so schedules, app events, and integration events are easy to tell apart. Review existing automations before creating a replacement to avoid duplicate runs. If a run fails or a connection is interrupted, inspect its history and the affected records before retrying: an action may already have completed. ## Authorize a paused schedule If a scheduled automation shows **Needs authorization**, anyone who may change its automations can choose **Authorize**. Review the saved task and confirm **Authorize and resume**. The automation then runs with your access. Keep **Automatically carry out the actions described in this task** off to retain its existing tool restrictions, or explicitly turn it on to pre-approve the actions described in the task. This does not grant additional app or connected-account access. Authorization keeps the automation's identity, task, schedule, and history. It does not run the task or replay missed occurrences: a future date stays unchanged, and a recurring schedule whose date has passed resumes at its next future occurrence. A one-time schedule in the past needs a new date first. Reviewing and authorizing the schedule does not launch an agent run or consume model credits.