# Automate weekly market intelligence briefs with Notion Custom Agents (full walkthrough) ## Метаданные - **Канал:** Notion - **YouTube:** https://www.youtube.com/watch?v=Tsr_O5Gp5Iw - **Дата:** 14.05.2026 - **Длительность:** 7:42 - **Просмотры:** 925 - **Источник:** https://ekstraktznaniy.ru/video/50802 ## Описание Learn how to automate a weekly market intelligence brief with *Notion Custom Agents* so your team stays ahead of competitor launches, pricing shifts, and key category news. In this walkthrough, we build an agent that scans curated sources, compiles a structured brief with links to every source, and posts a short recap to Slack. We also add guardrails (recent-only scope, caps per competitor, and “flag gaps instead of guessing”) and test the scheduled run. We’ll cover: - Setting up competitor/source URLs to monitor - Configuring Notion + Slack access and weekly scheduling - Adding guardrails for relevance and accuracy (linked claims only) - Formatting the brief (highlights, risks, opportunities, positioning, recommended actions) - Testing runs + troubleshooting in the activity log Resources: - Custom Agents help center: https://www.notion.com/help/category/custom-agents - More Custom Agents use cases: https://www.notion.com/product/ai/use-cases?page=0&feature=customAgent Follow Not ## Транскрипт ### Intro: what we’re building (weekly market intelligence brief) [] Hey everyone, I'm Sam from Notion. Today, I'm going to show you how to use custom agents to build a market intelligence briefing that keeps your team ahead of competitor moves. It scans your curated sources for competitor launches, pricing shifts, and key category news, then pulls it all into one brief with links to every source. And once it's set up, it just runs automatically every week. I'll walk you through how to build it from scratch. — ### Prompt the agent [0:32] — So, let's say that I need a weekly market brief that tracks competitor launches, pricing changes, and important category news so we can spot anything that might impact our next launch. Once we enter that prompt, the agent will start creating the initial structure of the build. As you can see, the agent is processing loading its tools, creating the relevant pages, and making sure that it's matching as best it can to the initial instructions. The agent's reporting back that it's set up, it's connected to both pages shared with everyone in Acme Labs. Turn that into can view. Market briefs, and there will be a couple more that we want to set up as well. So, let's start with what we need for our URLs. Here, we want to add a few URLs of potential competitors and what they've been up to. As you can see here, the agent has already set up every Monday at 9:00 a. m. that it will create a new page, but let's just make sure that in the weekly 9:00 a. m. briefing, when you create a new page in market briefs. ### Configure the output brief (risks, positioning tweaks, recommended actions) [2:01] Please flag risks, positioning tweaks, and recommended actions. Recommended actions for product and marketing. Then post a Slack message with two to three highlights and the page link. So, we can see that it's been able to connect with Slack and all public channels. Now, it's requesting channel info. And now it wants the channel name. So, now let's give the channel name that we want the agent to directly write into, and it's all competition market intel. So, we'll say give writing capabilities to all dash intel. ### Connect Slack + choose the channel to post highlights [3:06] So, now the agent will be able to look into our Slack and give those correct permissions. So, now we can see that the agent has access to that specific channel. Let's hit save. To make the contacts a bit stronger, in addition to market briefs, let's also give view access to our competitive one-pagers and Gong transcripts. So, here, just like with Slack, agent should be able to update its Notion access with the competitive one-pagers and Gong transcripts stock. Perfect. Save. Now, let's get a bit more specific about scope. We want to make sure that the agent only pulls updates that are both recent and relevant. So, let's say we want to update the instructions so the agent only looks at updates from the last 7 days. Cap summaries at two to three items per competitor. Another important thing would be to only include claims you can link to. If a source is missing or unclear, flag it instead of guessing. So, now with these scope instructions, agent will update its overall instructions page here to reflect the improved scope. So, now agent has updated the instructions and a great feature here is the show changes feature where agent will highlight the exact changes it made, so you can always change it back if needed or change it to something different. And here, we'll hit save once again. I already have a database here titled market briefs and this is where agent is adding pages. Let's now make sure that agent knows how to format the brief for each page it adds. So, let's say, "Please format your briefs in this way. Highlights, three to five bullets ### Add guardrails (last 7 days, caps per competitor, link every claim, flag gaps) [5:14] risks, opportunities, positioning tweaks, and recommended actions. " ### Set the brief format + test the scheduled run [5:26] Recommended actions. Product marketing. It will ask to continue updating its own instructions page. I've allowed it. And great, we have our revised structure. Now, I want to test the agent using the run agent button and see how the agent responds to that. So now let's test the Monday 9:00 a. m. scheduled run and things that I will be looking out for is if the agent is pulling from sources I intended, if the takeaways are feeling concrete, and especially important if every important claim that the agent is reporting on has a link back to the source. Great. So it was able to create the page that we wanted, which is the weekly market brief. There's the highlights, risks, opportunities, positioning tweaks, actions, and if there are any source gaps. But it wasn't able to complete the Slack message because see the name. So maybe I don't think I spelled it wrong, but let me let's make sure that we're seeing this right. Yes, all competition market intel. That says here. So let's just try to troubleshoot here. The name of the Slack channel is all competition market intel, please post there. So we can see here ### Troubleshoot + verify delivery (activity log + Slack post) [7:07] that the agent was able to post the brief. We can also look at the activity log which shows each run, what happened, and whether anything failed, which makes it a lot easier to troubleshoot if the brief looks off. And if something every does look off, I can just ask the agent to troubleshoot with me. And that's it. — Every Monday your team now gets a competitive brief, real sources, real risks, and tangible next steps without anyone having to manually compile it.