Log in Go Pro
Go Pro

Workflow Hub

Share your best AI workflow. We could show it to 2M+ people.

Every day, we feature the community's top-voted AI workflow in The Rundown newsletter.

New here? Say hi + tell us what you’re working on 👋

Whether you joined five minutes ago or you’ve been lurking for months, I want to meet you! Tell us who you are and one thing you’re trying to figure out with AI. I read and reply to every intro 💜 Comment below with: Who you are: your name, what you do, and where you’re based What you’re working on: one thing you’d love to automate, speed up, or figure out with AI Your favorite tool right now (bonus points if it’s one we haven’t heard of) Your LinkedIn, if you’d like to connect. Totally optional
Brooke Benson Question
10

Build a Custom Outlook Booking Page with Claude Code

I was about to start paying for a scheduling tool when I realized I would still be stuck with someone else’s rules. Instead, I built my own booking page with Claude Code. It took two hours to go from starting the project to going live, and I use it every day now. It’s a Next.js app on Vercel with no database. Availability is read live from my Outlook calendar through Microsoft Graph, so there’s nothing to sync or keep updated. My working hours come from my Outlook settings, so when I change my hours there, the booking page follows. When someone books, it creates the calendar event and generates the meeting link. The guest chooses Zoom or Teams on the booking page, so they can use their preferred platform. The rules are the main reason I built it. Same-day bookings are not allowed, so the earliest anyone can book is my next working day. If someone visits the page after hours or on a weekend, the following working day is blocked too. The app also counts back-to-back meetings before offering a slot: if booking that time would give me a run of more than four meetings in a row, the slot does not appear. There’s also a group link that only shows times when both my business partner and I are available. I also avoided doing the setup manually. I had Claude control my Chrome browser and handle the Microsoft and Zoom developer-console work while I did something else. Step-by-step: 1. I described what I wanted to Claude Code, and it built the first working version in one shot. I then gave it my preferences to refine the app. 2. I had Claude use browser control to create a Microsoft Entra app registration, add the application permissions Calendars.ReadWrite, MailboxSettings.Read, User.Read.All, and Mail.Send, and grant admin consent. 3. I did the same for a Zoom Server-to-Server OAuth app with the meeting:write:meeting:admin scope. Teams meetings are available through Graph, so Zoom was the only additional setup. 4. The availability route pulls working hours from Graph mailboxSettings and free/busy data from calendar/getSchedule, then computes open slots across a 21-day window. Only busy and out-of-office events block a slot, so tentative invites do not reduce my availability. 5. The booking route rechecks that the slot is still free, creates the event with the guest attached, creates the Zoom or Teams meeting based on the guest’s selection, and sends me a heads-up email. 6. I deployed the app to Vercel and proxied it from my own domain so the link lives on my site with my branding.
Dean Mazlish
  • Claude Code
7

Build a Custom Wedding RSVP and Seating Chart Workflow

Every RSVP tool I found wanted a monthly subscription to collect a few hundred yes-or-no answers, and none would return my data in a format I could use. So I built my own with Claude Code. The RSVP system is small: a form deployed on Vercel and embedded into our wedding website. We also emailed the direct link because plenty of guests might never visit the site. The form asks for more than a yes-or-no response. It collects meal choices, dietary restrictions, and plus-ones. Every submission adds a row to a Google Sheet through the Sheets API. That sheet ended up mattering more than the app. Months later, when it was time to create the seating chart, every guest was already represented in clean, structured rows that I could give to a completely different tool. For seating, I opened the same sheet in Claude and wrote out the rules in plain English: who had to sit together, who could not sit anywhere near each other, which relatives needed a quiet corner, and which friends could anchor a table of people who did not know anyone else. Claude produced a first draft that respected those constraints, along with an interactive board where I could drag people between tables. Step-by-step: 1. Tell Claude Code which fields you want on the RSVP form and have it build the front end and back end. Have Claude deploy it to Vercel. 2. Set up a Google Cloud service account, enable the Google Sheets API, and share the sheet with the service account’s email address. Configure each submission to append a row. 3. Embed the form on your wedding website and email the direct link separately. Some people will never open the website. 4. Ask for everything you will eventually need, not just attendance. Your caterer and venue will want meal counts and dietary restrictions, and going back to collect that information later is miserable. 5. When it is time to seat people, point Claude at the same sheet and write your rules in plain language: who must sit together, who cannot sit together, who needs a quiet table, and who can anchor a table of strangers. 6. Have Claude generate a first draft based on those rules, then move people yourself. This works anywhere you have a public form collecting data and a private tool that needs to reason about it. Put a spreadsheet between them instead of building one app that tries to do both. The form stays simple, and whatever you build six months later can read from the same place.
Dean Mazlish
  • Claude Code
4