# Configuring Triggers and Tools ### About this export | Field | Value | | --- | --- | | **content_type** | lesson | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/building-your-first-agent-in-agentos/configuring-triggers-and-tools | | **course_slug** | building-your-first-agent-in-agentos | | **lesson_slug** | configuring-triggers-and-tools | | **markdown_file_url** | /academy/md/courses/building-your-first-agent-in-agentos/configuring-triggers-and-tools.md | | **generated_at** | 2026-06-08T14:32:06.203Z | > Part of **[Building Your First Agent in AgentOS](https://www.contentstack.com/academy/courses/building-your-first-agent-in-agentos)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys. #### Video details #### At a glance - **Title:** Working with Triggers and Tools - **Duration:** 7m 19s - **Media link:** https://cdn.jwplayer.com/previews/B7pzchp8 - **Publish date (unix):** 1780760409 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113548 kbps - video/mp4 · 180p · 180p · 155670 kbps - video/mp4 · 270p · 270p · 177397 kbps - video/mp4 · 360p · 360p · 202471 kbps - video/mp4 · 406p · 406p · 218945 kbps - video/mp4 · 540p · 540p · 262816 kbps - video/mp4 · 720p · 720p · 342255 kbps - video/mp4 · 1080p · 1080p · 475644 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/B7pzchp8-120.vtt` #### Video transcript Okay, so we created a project and an agent. Now we're going to connect that agent to a real-world event. In our example, that event is the creation of a new article. Imagine an editor just completed writing an article. The core content is complete, but many of the enrichment fields remain empty. There's no teaser, there's no SEO description, and we don't have any tags. Before our agent can help, it needs to access that content. This lesson focuses on establishing that connection. We'll configure a trigger that responds when a new article is created. We'll then retrieve the article and verify that the agent can understand what was written. This is an important milestone. At this stage, we're not trying to modify content yet. We're simply proving that the agent can identify the content article, retrieve it, and reason about its content. So let's get into it. The first thing we have to do is we have to select a trigger. Again, a trigger is the thing that's going to make this agent do something. So on the right-hand side, we see there's all sorts of different triggers. We're going to go into CMS, and specifically what we want to do is find when an entry is created, and that's this first option right here. So I'll go ahead and select it. We need to tie our content stack account to this trigger, so I'll go ahead and click Add New Account. I'm going to have to authorize this, so I'll go ahead and click Proceed. It's going to tell me all the things that I'm authorizing for, and this looks good for our purposes. So again, I'll click Authorize. It may take a second. It has to log in, make sure that you are you, and then you'll have to select an organization. So I'll come over here and select that organization, and I have to give it a name. Content stack number one is default. For our purposes, that's fine, but again, you could be more specific here. Obviously, you want it to represent the name of the account that you're working with. I'll go ahead and click Save. Once I click Save, I can then come over and choose the stack that I want to work with. In this case, I'm going to choose this AgentOS Academy stack. I'm going to be working with the main branch. Now I have to select the content type. The type of content I'm working with is an article, so I'll go ahead and select that. You can also select an environment. In this case, maybe we want the agent to publish to the preview or the development server. It's completely up to you. I'll select Preview in this case, and once you're done, you can come over and click Save. That is the trigger. Now I want to show some way that this is actually working. I'm going to add a tool. I'll come over here and click Add. The tool that I want to use in this case is Slack. I use Slack here at Content Stack, so I'm going to go ahead and select it. After selecting it, I'm going to have to link it to my account, so I'm going to go ahead and have Slack use my credentials. Again, I'll go ahead and click Proceed. Again, it's just showing me everything that it's going to have access to. Again, I'm going to authorize that. It'll take a second. It'll have to come over, and you're going to have to verify that this is, in fact, okay. I'm going to allow this. I then have to set the account name. I'm going to call this Slack CS for Content Stack. Again, I'm a Content Stack employee. That's why I'm using Content Stack's Slack. So I'll go ahead and click Save, and then what we have to do is figure out how we want to send this message. In this case, I want to specify a particular channel, so instead of letting AI select the data, I'm going to add custom data. Then I can click this button here to open up a window, giving me the ability to select a particular channel. Now, there's all sorts of different channels here within the Content Stack instance of Slack, so I'm just going to load a few here until I think I find the channel that I want to work with. Then after loading enough, I can come up here and search the data. I'll go ahead and start typing in the name of the channel that I'm looking for, which is Slack Integration Testing. With that selected, that channel becomes visible. Now, in terms of the message and everything else, I'm going to let AI select this information as necessary. So I'll now come over and click Save. Once I click Save, I can then add some instructions for the agent, and it's just going to be in plain language. So I'm going to go ahead and type in, when a new article is created, and then I'm just going to give it a list of things to do. One, retrieve the article that triggered the workflow. Two, read the title, headline, and article body. Three, summarize the article. Four, send a message in Slack. And then you can come over and click Save. That's going to save the agent. And then in order for this agent to do anything, for it to listen for this event, we're going to have to publish it. So go ahead and click Publish. Again, you'll get a dialog box saying this action is going to publish the enrichment agent, which is what we want. So go ahead and click Publish. And now our agent is running, and it's listening for this entry created event. So now we can come back to the CMS. I'm going to go ahead and do that. And I'm going to come into AgentOS Academy. I'm going to then come into Entries. And from here, we're going to create a new entry. And this, of course, will be an article. I'll go ahead and click Proceed. And then I'm going to add the title. It will be Pacific Northwest Getaway. I just so happen to have text stored on my clipboard for the article body. I'm just going to paste that article. And once I'm done, I'm going to come over and click Save. And then that entry is saved. And now what I need to do is come over to Slack. And you'll notice I have a new notification telling me that the article Pacific Northwest Gateway was published. And I have a summary of what that article says. So the agent is doing its job. We're able to detect when an article is created. The agent is able to evaluate what the material inside the article represents. And it's able to do something with it, which in this case is just send a Slack notification. But we're well on our way to having this agent perform an enrichment protocol on entries that we create within Content Stack. #### Key takeaways - Connect **Configuring Triggers and Tools** 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 Configuring Triggers and Tools. Configuring Triggers and Tools in Building Your First Agent in AgentOS (building-your-first-agent-in-agentos). ### Retrieval tags - Configuring - Triggers - and - Tools - building-your-first-agent-in-agentos - lesson 05 - Configuring Triggers and Tools - building-your-first-agent-in-agentos lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "05" and topics: [Configuring, Triggers, and, Tools]. Parent course slug: building-your-first-agent-in-agentos. 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: Configuring Triggers and Tools | `https://cdn.jwplayer.com/v2/media/B7pzchp8/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/` |