title: Scheduled Report Rollup

description: A weekly workflow that pulls Stripe and Sheets data, reconciles the numbers, records the result, and posts the digest to Slack before the meeting.

import { VideoPlaceholder } from '@/components/ui/video-placeholder'

import { WhatYouWillLearn } from '@/components/ui/what-you-will-learn'

import { VideoChapters } from '@/components/ui/video-chapters'

<VideoPlaceholder eyebrow="Use case" title="Scheduled Report Rollup" className="mt-2" />

<div className="mt-8 grid grid-cols-1 items-start gap-10 lg:grid-cols-[1fr_300px]">

<div>

Let the Monday number assemble itself. A schedule fires each week, pulls the charges from Stripe and the tracking tab from Sheets, reconciles the two, computes the delta against last week, and posts the digest to Slack before anyone sits down for the meeting.

<WhatYouWillLearn

items={[

{ title: 'Run on a schedule', body: 'Trigger the rollup every Monday morning so the report is never late.' },

{ title: 'Reconcile two sources', body: 'Use a Function block to join Stripe and Sheets data and compute the delta.' },

{ title: 'Record and deliver', body: 'Write the result as a table row and post the digest to Slack.' },

]}

/>

</div>

<VideoChapters

chapters={[

{ title: 'The problem', time: '0:00' },

{ title: 'Schedule trigger', time: '0:35' },

{ title: 'Pull both sources', time: '1:10' },

{ title: 'Reconcile and compute', time: '2:00' },

{ title: 'Record and post', time: '2:50' },

]}

/>

</div>

A **Schedule trigger** fires every Monday at 7:00. The workflow pulls charges from the **Stripe API** and reads the tracking tab with **Google Sheets**. A **Function** block reconciles the two sources and computes this week's number and the delta. A **Table** block inserts the row, so every week's result is queryable later, and a **Slack message** posts the digest to the channel. Every run is recorded in the [logs](/logs-debugging).

This composes [workflows](/academy/workflows/intro) and [tables](/academy/tables/intro): the foundations, composed.

title: Telegram Personal Assistant

description: An assistant you text like a friend, it reads your inbox, checks your calendar, researches on request, and sends a morning brief on its own.

import { VideoPlaceholder } from '@/components/ui/video-placeholder'

import { WhatYouWillLearn } from '@/components/ui/what-you-will-learn'

import { VideoChapters } from '@/components/ui/video-chapters'

<VideoPlaceholder eyebrow="Use case" title="Telegram Personal Assistant" className="mt-2" />

<div className="mt-8 grid grid-cols-1 items-start gap-10 lg:grid-cols-[1fr_300px]">

<div>

Build an assistant you message like a friend. Each Telegram text, a question about your inbox, a calendar check, a quick research request, is routed to the right tools and answered in the same thread. A second trigger sends an unprompted brief every morning at 7:00.

<WhatYouWillLearn

items={[

{ title: 'Trigger from a message', body: 'Start a workflow from a Telegram text and reply in the same thread.' },

{ title: 'Route to the right tools', body: 'Use a Router so inbox, calendar, and research requests each take their own path.' },

{ title: 'Act without being asked', body: 'Add a schedule that assembles and sends a morning brief on its own.' },

]}

/>

</div>

<VideoChapters

chapters={[

{ title: 'The problem', time: '0:00' },

{ title: 'Telegram trigger', time: '0:35' },

{ title: 'Route the request', time: '1:15' },

{ title: 'Three agent lanes', time: '2:00' },

{ title: 'The morning brief', time: '3:00' },

]}

/>

</div>

A **Telegram trigger** starts the workflow on each incoming message. A **Router** block reads the request and picks a lane: an **Agent** that reads Gmail, an **Agent** that checks Google Calendar, or an **Agent** that researches the web with Exa. Whichever lane runs, the answer goes back as a reply in the same Telegram thread. A second **Schedule trigger** fires daily at 7:00, a brief agent gathers the day's context, and a **Telegram send** delivers it before you ask. Every run is recorded in the [logs](/logs-debugging).

This pulls together [workflows](/academy/workflows/intro) and [agents](/academy/agents/intro) into one system: the foundations, composed.

title: WhatsApp Storefront Bot

description: A shop that answers at any hour, a WhatsApp bot that replies from your FAQ with cited answers, remembers the conversation, and escalates refunds to you.

import { VideoPlaceholder } from '@/components/ui/video-placeholder'

import { WhatYouWillLearn } from '@/components/ui/what-you-will-learn'

import { VideoChapters } from '@/components/ui/video-chapters'

<VideoPlaceholder eyebrow="Use case" title="WhatsApp Storefront Bot" className="mt-2" />

<div className="mt-8 grid grid-cols-1 items-start gap-10 lg:grid-cols-[1fr_300px]">

<div>

Build a shop that answers at any hour. Each customer message on WhatsApp is checked against the shop's FAQ, answered in-thread with citations, and remembered, so the next message from the same customer picks up where the last one left off. Refunds and complaints skip the bot and land in your Slack.

<WhatYouWillLearn

items={[

{ title: 'Trigger on a customer message', body: 'Start a workflow from a WhatsApp message and reply in the same thread.' },

{ title: 'Ground the answer', body: 'Search a knowledge base of the shop FAQ so replies are accurate and cited.' },

{ title: 'Remember the customer', body: 'Use conversation memory keyed to the sender so follow-ups stay in context.' },

]}

/>

</div>

<VideoChapters

chapters={[

{ title: 'The problem', time: '0:00' },

{ title: 'WhatsApp trigger', time: '0:30' },

{ title: 'Escalate refunds', time: '1:10' },

{ title: 'Answer from the FAQ', time: '1:50' },

{ title: 'Remember the thread', time: '2:45' },

]}

/>

</div>

A **WhatsApp trigger** starts the workflow on each customer message. A **Condition** block checks it first: refunds and complaints route straight to the owner's **Slack**, everything else continues. A **knowledge-base search** pulls the relevant FAQ entries, and an **Agent** block with [conversation memory](/academy/agents/memory) keyed to the sender writes the reply, so each answer is cited and each thread remembers its history. The **WhatsApp reply** goes back in the same conversation.

This pulls together [workflows](/academy/workflows/intro), [agents](/academy/agents/intro), and [knowledge bases](/academy/knowledge-bases/intro) into one system: the foundations, composed.