01
Saved versions and deployment
Save a new version when the workflow changes. Deploy the version that future live runs should use; existing runs keep the version they started with.
Automation conceptsAutomations
What are Automations in Tale?
Automations make recurring project work repeatable. Connect model calls, agent steps and actions into a versioned workflow, test it, and run it manually or through a configured trigger.
How automations run in Tale
Define the process, choose the steps and data it needs, and inspect each run. Configure approval policies for protected connector writes.
01 Approvals
Human-in-the-loop before it ships
When policy requires approval, a connector write waits for a person. Approval lets the run attempt the action; rejection blocks it.
02 Agents
Give an agent a workflow step
Configure an agent step with its own runtime, model, instructions and equipment. Use a model call when a single response is enough.
03 Knowledge
Supply the sources the process needs
Add knowledge retrieval or stage reference files where the workflow needs them. Pass the results to later steps and inspect their outputs.
04 Projects
Scope workflows by workspace
Bind an automation to the projects where it belongs. Project access and the tools granted to each step determine what it can reach.
Define and repeat the process
Keep the steps, saved versions, triggers and run history together so the team can inspect how recurring work is performed.
02
Typed workflow steps
Combine model calls, sandboxed agent work, data transformations, subautomations and connected actions. Add conditions or iteration where supported.
Workflow editor03
Triggers that fit the job
Schedules (cron), webhooks, platform events, or a manual test run from the editor.
Triggers04
Execution logs
Inspect a run’s status, inputs, outputs and step trace. Review recorded connector effects when checking what happened.
Execution logs05
Approvals in the loop
Connector policies can pause protected writes for approval. An agent step can also ask a person for missing information before continuing.
Automation concepts
Automations FAQ
An automation defines a repeatable workflow with inputs, steps and outputs. Saved versions, deployment, triggers and run history let your team test and operate that process.
No. A workflow lives inside its automation. The automation's Editor tab is where you meet the graph.
Use an automation for repeatable steps, conditions, schedules or connected actions. Use a project agent when a task needs an outcome that you will review. An automation can include agent work.
Yes. Test a saved version before deploying it or enabling a trigger. Mock runs simulate connector operations; live runs can affect connected systems and may require approval.
Work you can try with your team
Start with a clear brief, defined deliverables, and a review process.
See your team’s next workflow in Tale
Bring a task to a guided demo, or start a workspace and try it with your own agents.