01
Installable bundles
Owners and Admins install from the catalog; Members use the Inbox, agents, or views it registers without assembling pieces by hand.
Automation conceptsAutomations
What are Automations in Tale?
An automation bundles integrations, agents, a workflow, and the views it ships — an Inbox, for example — into one installable unit. The workflow inside is a graph of typed steps — LLM, Action, Condition, Loop, Sandbox — with schedules, webhooks, events, and human approvals.
How automations run in Tale
Chain triggers, LLM steps, and actions — then approve what ships and ground every step in knowledge.
01 Approvals
Human-in-the-loop before it ships
The run pauses where you told it to. Approve releases the held step with a journal entry; reject stops the run cold.
02 Agents
Call the right agent as an LLM step
Workflows pick specialists the same way Chat does — instructions, knowledge, and tools travel with the step.
03 Knowledge
Ground every step in indexed sources
The pipeline's LLM steps read from vendor contracts, the ERP field map, and the supplier crawl — every classification cites the source it used.
04 Projects
Scope workflows by workspace
Projects keep automations, agents, and members together so ops runs stay out of engineering.
What ships in an automation?
Compose multi-step work as a typed graph — LLM, action, condition, loop, and sandbox steps — with approvals and versioned runs.
02
Typed workflow steps
LLM, Action, Condition, Loop, and Sandbox steps compose the graph. Every save snapshots a version you can restore.
Workflow editor03
Triggers that fit the job
Schedules (cron), webhooks, platform events, or a manual test run from the editor.
Triggers04
Execution logs
Every run records status, timing, inputs, and a per-step journal — audit trail and debugger in one place.
Execution logs05
Approvals in the loop
Proposed workflow edits, agent-started runs, and waiting-for-input pauses land as approval cards before work continues.
Automations FAQ
A Tale automation is an installable bundle — integrations, agents, a workflow, and ready-made views like an Inbox — that runs multi-step work with triggers and approvals.
No. A workflow lives inside its automation. The automation's Editor tab is where you meet the graph.
Use an automation when the job needs multiple steps, branches, schedules, or approvals between them — not when a single conversational agent is enough.
Yes. The editor has a manual test run — you watch a complete execution with inputs, a per-step journal, and timing before any trigger goes live.
See Tale on your stack
Book a guided demo or talk to the team about self-hosted deployment, pricing, and hardware.