# Agents vs Automations ### About this export | Field | Value | | --- | --- | | **content_type** | lesson | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/agentos-foundations/agents-vs-automations | | **course_slug** | agentos-foundations | | **lesson_slug** | agents-vs-automations | | **markdown_file_url** | /academy/md/courses/agentos-foundations/agents-vs-automations.md | | **generated_at** | 2026-06-19T08:30:58.340Z | > Part of **[Agent OS Foundations](https://www.contentstack.com/academy/courses/agentos-foundations)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys. #### Video details #### At a glance - **Title:** Agents vs Automations - **Duration:** 4m 12s - **Media link:** https://cdn.jwplayer.com/previews/K1x64ULw - **Publish date (unix):** 1780928262 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113770 kbps - video/mp4 · 180p · 180p · 175497 kbps - video/mp4 · 270p · 270p · 217438 kbps - video/mp4 · 360p · 360p · 256553 kbps - video/mp4 · 406p · 406p · 272259 kbps - video/mp4 · 540p · 540p · 346673 kbps - video/mp4 · 720p · 720p · 456447 kbps - video/mp4 · 1080p · 1080p · 729919 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/K1x64ULw-120.vtt` #### Video transcript We just talked about the idea that agents and automations are different. Now let's explore exactly what that means. Because one of the biggest mistakes organizations make when they first start working with AI is trying to use an agent for everything. In reality, automations and agents solve different problems. Let's start with automation. Most automation platforms operate using a very simple model. Something happens, a trigger fires, then a predefined sequence of actions executes. For example, imagine a content editor publishes an entry. When that happens, we might automatically send a Slack message, update a project board, and notify a stakeholder. Every step is known ahead of time. The workflow is predictable. If the same trigger happens tomorrow, the exact same steps will execute again. That makes automations powerful, it's reliable, it's repeatable, and it's often the right solution. But, now let's look at a different problem. Suppose I ask a system to find the most important AI stories from this week, summarize each one, explain its impact on digital experiences, create content entries for the findings, and then notify my team. Suddenly, the workflow becomes much less predictable. The system may need to search different sources. It might discover different stories. It may decide one story is more important than the other. It may need to generate different summaries every time it runs. This is where agents become valuable. Instead of following a fixed sequence of steps, an agent is given an objective. The agent then determines how to achieve that objective using the tools and instructions available to it. The important distinction is that the desired outcome stays the same, but the path may change. That's a fundamentally different way of thinking about software. One of the useful ways to think about this is, automations know how, agents know what. An automation already knows exactly how a task should be completed. An agent knows what outcome you're trying to achieve and has the flexibility to determine how to get there. Now, that flexibility is powerful, but it also introduces tradeoffs. Automations are highly predictable. Agents are adaptive. Automations are easy to test because the workflow rarely changes. Agents can produce different outputs based on the information they discover and the decisions they make. That's why the question isn't whether agents replace automations. The question is when to use each. If the workflow is straightforward, repeatable, and requires consistency, automation is usually the better choice. If the workflow involves research, analysis, content generation, decision support, or other forms of knowledge work, an agent may be the better fit. In practice, the most successful organizations often combine both approaches. An agent determines what needs to happen, and automation handles the predictable operational work. Together, they create systems that are both intelligent and reliable. As we move through these series of courses, you'll see this pattern repeatedly. The goal isn't to replace every automation with an agent. The goal is to identify the right problems for agents to solve. #### Key takeaways - Connect **Agents vs Automations** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ## Supplement for indexing ### Content summary Agents vs Automations. Agents vs Automations in Agent OS Foundations (agentos-foundations). ### Retrieval tags - Agents - Automations - agentos-foundations - lesson 02 - Agents vs Automations - agentos-foundations lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "02" and topics: [Agents, Automations]. Parent course slug: agentos-foundations. Use asset_references URLs as thumbnail hints in search results when present. Never surface LMS quiz content or assessment answers from this file. ### Asset references | Label | URL | | --- | --- | | Video thumbnail: Agents vs Automations | `https://cdn.jwplayer.com/v2/media/K1x64ULw/poster.jpg?width=720` | ### External links | Label | URL | | --- | --- | | Contentstack Academy home | `https://www.contentstack.com/academy/` | | Training instance setup | `https://www.contentstack.com/academy/training-instance` | | Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` | | Contentstack documentation | `https://www.contentstack.com/docs/` |