Knowledge and workspace tools
Automations
An automation runs a defined follow-up when a supported event occurs. It is useful when the same safe process should happen every time, such as handling a form submission or routing a known kind of work.
Start with a clear trigger and outcome
Write down the trigger, the action and what counts as success before enabling an automation. Keep the first version narrow. An automation should not hide a decision that still needs a person to make it.
Open Workspace → Automations to see configured automations, whether they are enabled and whether any work has been left unrouted. Pause an automation when you need to stop new runs while you investigate a problem.
Use the agent route carefully
An agent can manage automation configuration through manage_automation. Ask it to describe the trigger, actions and any destination before it creates or enables anything. Test with a safe example where possible and read the result back.
A prompt to try
List this workspace’s automations. For each one, show its trigger, whether it is enabled and any recent failure or unrouted work. Do not change anything.
Design an automation for this form submission. State the trigger, each action, who should receive the outcome and how we will test it. Do not enable it yet.
Monitor after enabling
Enabled does not prove an automation produced the right result. Review its first run, check the destination and keep an eye on failures or unrouted work. Update the automation when the underlying form, task process or destination changes.
See Forms and surveys, Dates and recurring work and Skills.