Daily AI Brief Starter
Research a narrow topic, review the cited brief, and test delivery through an authorized connection.
The daily_ai_brief template prepares a scope, calls web.search, and maps the resulting citations and summary into a chat.generate step. It passes the draft to an approval node, then uses reviewApproved to choose the send or revise branch. The message.send step has its own approval requirement.
| Input | How the draft uses it |
|---|---|
briefTopic, sourceRefs | Required text. The search node uses these inputs as its query and source scope. |
deliveryChannel | Required text mapped to the send step. Configure the actual connection and recipient resource. |
reviewApproved | Required Boolean that selects the branch after the approval node. |
scheduleHint, reviewSummary | Optional timing context and review notes. The new draft has a manual trigger. Configure the schedule separately. |
{
"briefTopic": "Summarize important changes in this week's test source set",
"sourceRefs": "Test changelog\nInternal test editorial notes",
"deliveryChannel": "Operations test destination",
"scheduleHint": "Weekdays at 09:30",
"reviewSummary": "Check the date range and each citation",
"reviewApproved": false
}- Replace the source examples with references your search setup can use. Confirm the brief distinguishes its findings and includes the citations you expect.
- Use
falseto verify the revise branch. When testing send, bind a connection and approved test recipient. If your workspace exposes a Send a message with … Channel action, select it for that resource and map the brief to the message text it expects. - In a separate approved test run, use
trueand inspect the send receipt. The final Delivery node needs a supported project target and an artifact. If you need a project record, save the brief or receipt as a document artifact and connect it to Delivery. For repeat runs, configure scheduled tasks after the delivery route is verified.
See App connections and Research workflows.