> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/august-1-2025.md).

# August 1, 2025: Real-time workflow context sidebar

### **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/mR80Z8_rGx0>" %}

### Contents of the Recording:

* 🎤 Intro: Aharon welcomed participants and outlined the call’s purpose and technical focus.
* 💡 Ashe shared community updates, upcoming events, and announced the International Cat Day photo competition for Rewst.
* 📣 Clea recapped new ROI series, training updates, certifications, and documentation enhancements.
* 🛠️ JP reviewed marketplace status, recent bug fixes, and plans for workstation offboarding crates.
* 🔧 Danial detailed integration fixes, improved testing, upcoming features, and hourly dashboard updates.
* 🧠 Pizza demonstrated the new real-time workflow context sidebar and variable exploration in the editor.
* 🔒 Aharon presented a local administrator password rotation workflow for multiple OS environments.
* 📞 Logan explained the process of converting Asterisk REST specifications and integrating them into Rewst.
* 🤖 Chris Williams showcased an AI-driven after-hours call handling workflow with multi-channel alerts.
* 📬 Nick introduced an email forwarding scheduling tool with delay workflows and thread management.
* ❓ Q\&A: Participants engaged in troubleshooting, feature questions, and shared feedback.
* 🏁 Outro: Ashe and Aharon closed the session, encouraged Discord engagement, and previewed the next Open Mic.

<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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/august-1-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.