# June 20, 2025: The PSA Automations That Quietly Saves Hours Every Week

### **Join Live!**

Join us live every Friday at 3 pm EST!

[Download the Calendar Invite here](https://engine.rewst.io/webhooks/custom/trigger/02eb02e2-1177-43d9-9e13-8547414979fc/c47fdd7f-4075-47a8-ba92-94e790e67c06?request_type=open_mic_link&)!

## Open Mic Video Recording

{% embed url="<https://youtu.be/i7W-u-n6HB8>" %}

### Contents of the Recording:

* 🎙️ The session opens with a welcome from Aharon, who emphasizes the importance of asking questions for MSP success and highlights the upcoming FLOW event.
* 💬 Ashe introduces the technical nature of the session and hands it off to George, who encourages attendance at FLOW and shares community best practices.
* 📱 Brooke provides a developer update, showcasing new app builder features, dashboard improvements, and workflow filtering upgrades.
* 🔧 Riggs details a major fix that significantly reduced workflow initialization failures through backend optimizations.
* 📊 Brooke presents a new workflow executions widget for the dashboard, clarifying its recent launch and data availability.
* 🛠️ George gives a demo of new app builder features including updated themes, reset buttons, background customization, and layout presets.
* 🧰 JP introduces a new Windows Patch Deployer crate and previews upcoming marketplace additions, including BitLocker-focused workflows.
* 🎓 Clea shares certification shoutouts, upcoming training, a course preview, and tips for navigating unfinished courses in CluckU.
* 🏃 Ben demos a wellness contest workflow that integrates forms, Slack, SQL, and block kit to create an interactive engagement tool.
* 📋 Hunter presents a workflow that ensures ConnectWise tasks are completed, automatically notifies users, and prevents duplicates with Ginga logic.
* 🔁 Derek shares a subworkflow for setting ticket statuses in ConnectWise using board lookups and status name-to-ID matching.
* ⚙️ Stuart walks through a dramatically optimized auditing workflow for client devices using SQL caching and ID normalization.
* 🗣️ The open mic begins with Aharon teasing surprises for FLOW, including ideas like a promotional chicken suit for the event.
* 🧪 Andrew raises an issue with DNS Filter user retrieval, which sparks a group troubleshooting session about API limitations and endpoint access.
* 🧵 Jeffrey demos a mirrored ticketing system and gets help resolving an issue with duplicate notes through custom field locking suggestions.
* 🎤 The session closes with open Q\&A and final comments from Aharon about the upcoming FLOW keynote and conference excitement.

<details>

<summary><strong>How to Get Help</strong></summary>

* 💬 Chat (Discord): [https://discord.gg/rewst​​](https://discord.gg/rewst%E2%80%8B%E2%80%8B)
  * Private #{{ msp }} channel
  * \#the-kewp
* 🎫 Submit Tickets to: <the_roc@rewst.io>
* 📝 Feature Request + Integration Requests: <https://rewst.canny.io/>

**CLUCK UNIVERSITY – REWST TRAINING:**

* 👨‍🏫 Live Instructor-Led Training: <https://calendly.com/cluck-u/>
* 🏁 Rewst Foundations Training: <https://docs.rewst.help/cluck-university/rewst-foundations-10x>
* ▶️ On-demand Videos: <https://docs.rewst.help/cluck-university/rewst-foundations-10x>

**DOCS:**

* 🥚 Rewst Docs: <https://docs.rewst.help>
* ⛩️ Jinja Docs: <https://jinja.palletsprojects.com/>

**KEY LINKS:**

* 📝 Feature Request + Integration Requests: <https://rewst.canny.io/>

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/june-20-2025-the-psa-automations-that-quietly-saves-hours-every-week.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.