> 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-europe/2025-roc-open-mics-europe/july-3-2025-secret-ai-sneak-peek-and-next-level-crates.md).

# July 3, 2025: Secret AI Sneak Peek & Next-Level Crates

### **Join Live!**

Join us live on the first Thursday of every month at 3pm GMT

[Download the Calendar Invite here](https://go.rew.st/open-mic?hs_preview=BFeQDWBI-187816500244)!

## Open Mic Video Recording

{% embed url="<https://youtu.be/MY4vnM-ev8s>" %}

### Contents of the Recording:

* 🟢 George welcomes everyone to the Rewst EU Open Mic, kicking off our monthly update and community collaboration space.
* 📊 Danial presented June’s product highlights including the dashboard workflow table, forms options filters, enhanced workflow result filtering, marketplace redesign, new integrations, and previewed RoboRewsty AI functionality.
* 🛒 JP detailed several new and refactored crates released in June with improved supportability, including Windows Patch Deployer, security integrations, and expanded automated unit testing.
* 🎓 Clea encouraged attendees to leverage Cluck University courses this summer, announced deprecation of seven micro courses, and highlighted process engineering and automation basics offerings.
* 🎉 George shared upcoming Flow 2026 early bird pricing, NinjaOne webinar, Discord channels, community creation videos, and business leaders focus groups .
* 🔗 Gareth demonstrated a two-way integration between ClickUp and Rewst workflows and tickets, showcasing task creation, updates, and synchronization with ClickUp tasks and ConnectWise tickets.
* 🚀 The session concluded with an open Q\&A, reminders for August’s EU Open Mic, and an invitation to join the fun open mic event tomorrow.

<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-europe/2025-roc-open-mics-europe/july-3-2025-secret-ai-sneak-peek-and-next-level-crates.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.
