Community

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. One post will put you on the radar of top founders, hiring managers, and operators across the industry.

Welcome!

Documentary film archival research bot

I’m researching two separate documentary films. For each project, the bot runs three web crawls and one health check every day. Based on my notes, scripts, and other existing initial research, it identifies research domains by theme and media type, favoring audio and images while applying a higher threshold to other documents. Anything scoring eight or higher is logged in Notion and downloaded automatically when possible. The bot cycles through different themes, and the health check adjusts the similarity threshold based on the results. If many items score eight, it may log and download only nines. If fewer qualifying items appear, it may begin downloading sevens. Most items cannot be downloaded because they are inaccessible to the bot, but they are still logged and linked. I review the items in Notion and mark each one according to criteria such as “people only for research” or “reject—permissions required.” It isn’t a full replacement for professional archival research, but I feel it’s getting me 90% of the way there. As an independent filmmaker, this is a huge benefit. Each morning, it sends me a synopsis, and each week, it sends me a list of pre-written emails to send to archives that require human interaction. Step-by-step: 1. I provide the bot with my notes, scripts, and existing initial research for each documentary project. 2. For each project, the bot runs three web crawls and one health check every day. 3. It identifies research domains by theme and media type, with a preference for audio and images and a higher threshold for other documents. 4. It logs items scoring eight or higher in Notion and automatically downloads them when possible. 5. It cycles through different themes and uses the health check to adjust the similarity threshold: it may focus on nines when many eights appear, or begin downloading sevens when fewer qualifying items appear. 6. It logs and links items that cannot be downloaded because they are inaccessible to the bot. 7. I review each item in Notion and mark it according to criteria such as “people only for research” or “reject—permissions required.” 8. Each morning, I receive a synopsis, and each week, I receive pre-written emails for archives that require human interaction.

Tools used
Industry
4

Create a five-day sermon follow-up text series from a previous Sunday’s sermon

I created a Gemini Gem with custom instructions. When I paste a link to the previous Sunday’s sermon, the Gem “watches” the video and creates five messages—one for each weekday. Each message uses a specific engagement method, such as a link to watch the sermon for anyone who missed it, a graphic featuring a verse from the sermon, or a reflection question tied to the sermon’s theme. After I approve the copy, the Gem creates a properly formatted Google Sheet in my Google Drive, ready to be dragged and dropped into our text provider. Within five minutes, I have content deployed that extends the impact of the 45-minute sermon throughout the week. Step-by-step: 1. I paste a link to the previous Sunday’s sermon into my Gemini Gem. 2. The Gem watches the video and creates five weekday messages. 3. I review and approve the copy for each message. 4. The Gem creates a correctly formatted Google Sheet in my Google Drive. 5. I drag and drop the content into our text provider for deployment.

Tools used
Industry
#communication#gemini#gems#graphics#image
0

Automate Security Risk Assessment Reports in 15 Minutes

Earlier in my career, I spent a significant amount of time delivering security risk assessments. These engagements typically took 8–12 weeks from the initial client meeting to the final report, with complex projects often stretching to 3–4 months. Today, I can produce reports of comparable quality in 1–2 days. The automation runs end-to-end in about 15 minutes; I spend the remaining time reviewing and validating the output. The workflow starts with a structured questionnaire and uses ChatGPT, Perplexity, Claude, Make.com, Google Drive, and Gamma.ai to research, draft, format, and deliver the report. This compresses the delivery timeline while preserving quality and lets me focus on expert judgment, validation, and client communication instead of manual report production. Step-by-step: 1. I have the client visit a web page and complete a structured questionnaire built on Lovable.dev. 2. The submitted information triggers an automated Make.com workflow. 3. ChatGPT analyzes the client’s responses. 4. Perplexity conducts targeted research tailored to the client’s industry, context, and risk profile. 5. Claude drafts the report and saves it to Google Drive. 6. The draft is passed to Gamma.ai, which generates the final client-ready report. 7. I receive the report by email, perform a thorough review, and send it to the client once I approve it. 8. I use the time saved to focus on expert judgment, output validation, and client communication.

Tools used
Industries
1