Daily operations briefing.

The problem explored

Turning operational inputs into a briefing, with conditional calendar creation.

A scheduled briefing flow that can add a calendar event and distribute an update. The supplied diagrams document the configured connections, rather than verified production outcomes.

Inside the processing logic

Start a scheduled run

• A Schedule Trigger feeds an If node.
• The selected route reads Google Sheets.
• The configured schedule and sheet fields are not visible.

Prepare the briefing

• An AI Agent connects to Gemini.
• A Filter node follows the agent.
• A code node prepares data before another If node.

Branch on a condition

• The second If node has two outgoing routes.
• One route includes Google Calendar Create Event.
• The other route bypasses the calendar step.

Distribute the update

• Both routes lead to a Gmail send-message step.
• A Slack send-message node follows Gmail.
• Recipients and message content are not exposed by the screenshot.

Step through the explanation

Dennice, an original illustrated robot guide, walks through the diagram. Start with Next, or choose autoplay. Captions and a full transcript are included; sound is optional.

Open the film on its own

Source evidence

These are the supplied local files used to write this explanation. Node labels and connections are visible; exported workflow JSON and execution logs were not supplied.

Visible outputs

Gmail and Slack updates, with a calendar event on one conditional route.

These outputs are represented by nodes in the source. Delivery success and business results require execution evidence.

What this case study does—and doesn't—verify

Next validation steps

Before operational use, I would inspect the workflow export, confirm credentials and permissions, test representative inputs and error paths, and review the outgoing messages with the intended user. These are proposed checks, not completed workflow execution tests.