At most one email a week. Unfollow anytime with one click.
Transcript
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Show transcript
Introduction
Hi, and welcome back to Claude from Zero to Expert. This is the closing practice episode of the Connectors and Integrations session. It's time to put everything we've learned together. We'll build a connected morning workflow: one request, and Claude reads the calendar, email, and documents at once, then writes a briefing that's ready to act on.
Step 1: Designing the morning flow
In earlier episodes we used connectors one at a time. Drive for documents, Gmail for email, the calendar for schedules. Today we combine them. The goal is clear: a morning briefing in five minutes. One request, three apps read, and the result is a single page that's ready to act on. Our example is still Dewi at Maju Bersama Co., whose mornings we already know: a full inbox, a packed calendar, and documents scattered across Drive. Before writing the request, design the flow. Part one, today's schedule from Google Calendar. Dewi needs to know when she's tied up in meetings. Part two, urgent emails from Gmail since yesterday afternoon. Not every email, only the ones that need action today. Third, meeting material. If there's a meeting today, Claude finds the related documents in Drive and summarizes them. Fourth, three priorities. Claude builds them from the schedule, emails, and documents. Only three, to stay focused. Fifth, a list of drafts that need approval. Claude may prepare them, but Dewi decides. Notice that the first four parts only read. Designing it first like this makes our request clear. Claude knows what to read, in what order, and where it must stop and wait for Dewi.
Step 2: Saving the instructions in a Project
Writing a request this long every morning would be a hassle. So we save it as standing instructions. Part one, the data: today's calendar, email since five o'clock yesterday afternoon, and Drive documents for today's meetings. Part two, the format: the schedule, three priorities, urgent emails, and drafts that need approval. The order is always the same, so Dewi can read it quickly. Part three, the permission limits, the most important part: read only. Don't send, invite, or delete anything without approval. Part four, an example. Dewi prepares one briefing she likes, so the style of the result stays consistent every day. Dewi creates a new Project called Dewi's Morning Briefing, then pastes those instructions into the project instructions field. Notice the last sentence: without my approval. She adds the Operational Priority Rules file. It holds office policy, for example that school orders and critical stock always come first. Then the Good Briefing Example file, as a guide for style and length. These files aren't sensitive data, just work rules. Finally, the priority customer list. Notice its description: only store and school names, with no phone numbers or addresses. Claude doesn't need contact details to set priorities. From now on, every morning Dewi just opens this Project and types one short sentence: this morning's briefing. Claude reads the instructions and files from the Project.
Step 3: Running the morning briefing
Thursday morning. Dewi opens the Morning Briefing Project and types just three words: this morning's briefing. Claude starts with Thursday's calendar. The first tool line shows Google Calendar being read. Then Gmail: twenty-four emails since yesterday afternoon. Then Drive. Because there's a supplier review meeting today, Claude looks for its meeting material. Three apps are read in turn, without Dewi switching windows. Claude gives a one-sentence summary and prepares the full briefing. Let's look at the result. Here's the briefing in the Artifact panel. At the top are three numbers: two meetings, two urgent emails, and two drafts waiting. Below that is a table of three priorities, with reasons and sources. The source column matters, so Dewi knows which app each piece of information came from. At the bottom are two drafts waiting for approval. Dewi doesn't just take it on trust. She asks: why is the Harapan Junior High delivery priority number one? Claude explains: the office priority rules put school orders first, and there's a new email from Ms. Sari this morning. The reasoning makes sense and can be checked. Then Dewi asks for a summary of this afternoon's meeting material in just three lines. Claude summarizes three suppliers from the documents in Drive: cheapest but often late, a minimum order, and most punctual. The meeting material is ready without Dewi opening a single file.
Step 4: Following up with approval
A briefing is only useful if you act on it. Dewi asks Claude to show the second draft, the review meeting invitation. The draft is complete: title, time, attendees, and a note that the supplier summary is attached. It's still marked as not sent. Dewi remembers Andi is at the warehouse until noon. She changes the time to two o'clock, and only then gives permission to send. Sending an invitation is a level-three action, so it only runs after Dewi clearly approves. The tool line records that approval. Claude confirms the invitation was sent, and reminds her that the draft for Ms. Sari is still waiting for a decision. Notice the pattern. Claude prepares, Dewi checks and fixes, then Dewi gives permission. Nothing gets sent just because Claude thinks it's right. Before approving any action from the briefing, use these four questions. First, is the source clear, and have you checked it if it's important? Second, are the names, dates, times, and numbers correct? The example showed that one wrong time can derail a meeting. Third, are the recipients right, with no unnecessary data going along? Fourth, are you ready to take responsibility for this action? If not yet, hold off. Tomorrow morning's briefing will remind you again.
Step 5: Apply it to your work
Anyone can use the same pattern. Laras reads order emails, the production calendar, and the price list, and gets a summary of today's orders and the supplies to buy. Mr. Hendra reads his class calendar, emails from parents, and teaching material in Drive. His briefing holds today's classes, the materials to bring, and messages that need a reply. Nadia reads her posting calendar and all her client emails. Her briefing is grouped by client, including revisions requested yesterday. For Nadia, remember the rule of a separate account per client. Now it's your turn. Start with a simple version, run it for three days, then improve the instructions based on what's missing. Three next steps. First, run the briefing every morning for a week, and note the parts you correct most often. Second, improve the Project instructions from those notes. For example, Dewi adds a rule that stock below fifty reams always counts as a priority. Remember, the screens in this video are simulations, and menu names may differ because Claude is updated often. Third, in Claude this flow runs when you ask for it. If you want the briefing delivered automatically every morning without opening Claude, continue to the Agentic AI Without Coding class at cerdasinovasidigital.com.
Done!
Congratulations, the Connectors and Integrations session is complete. We designed a morning flow, saved it in a Project, ran a briefing from three apps, and followed up with approval. In the next session Claude goes further: working directly in the browser, opening web pages, and filling in forms. We start by getting to know Claude in Chrome. See you there!
Practice exercises
Try these on your own after watching to lock in what you learned.
Create a morning briefing Project with your own version of the instructions
Run the briefing three days in a row and note what needs improving
Add one new priority rule to the instructions after the third try
Ask the class material
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
My notes
Notes are saved with the current video time and are only visible to you.
Questions & answers
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.
Your instructor
Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
53 video classes1,291 episodes
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
