> 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/march-21-2025-showing-the-first-workflow-we-ever-made.md).

# March 21, 2025: Showing the First Workflow We Ever Made

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

### Contents of the Recording:

* 🚀 Aaron kicks off the session with reminders about using Discord and the upcoming Flow conference and celebrates 100% uptime across Rewst environments.
* 🛠️ Daniel shares updates, including better error messages, persistent table sorting, bug fixes, and a sneak peek at upcoming features like the Powershell-Jinja integration.
* 🎓 Brandon announces new certifications, shares kudos for recently certified users, unveils a sneak peek at the LMS, and reviews updated documentation.
* 💬 George encourages community sharing via the Workflow Forum on Discord and highlights recent helpful workflow posts.
* 🐣 \[Internal Demo] Ashe shares the first workflow she ever built, highlighting the importance of starting small and learning iteratively.
* 📅 \[Internal Demo] Ashley and Tim explain how a web hook-powered workflow sends ICS calendar invites through Rewst using query parameters and proper MIME types.
* 🔁 \[External Demo] Brian walks through how his early monolithic workflow evolved into modular sub-workflows that automatically manage Rewst user invites.
* 🌐 \[External Demo] Mendy demonstrates how he turned Rewst into a content server that powers a Halo ITSM portal with dynamic speaker scheduling and ICS invite automation.
* 🧩 The group reflects on growth, learning, and building automation over time, sharing advice on starting small, iterating, and collaborating.
* 👏 Ashe wraps up the call, encouraging new community members to demo and thanking all contributors.

<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/march-21-2025-showing-the-first-workflow-we-ever-made.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.