> 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/2023-roc-open-mics/march-3rd-2023-new-webhooks-tracking-steam-deals-and-templates-oh-my.md).

# March 3, 2023 - New Webhooks, Tracking Steam Deals, and Templates? Oh my!

This call is for people who are:

* Interested in building their own workflows
* Wanting to stay on top of new developments
* Want to learn more about Rewst and participate in the community
* We will talk about the platform, news, some training, and any Q\&A.
* As always, feel free to unmute and interrupt us, this is an interactive call!

{% embed url="<https://www.youtube.com/embed/qtFVJbgJcOE>" %}

## Contents of the recording

<details>

<summary><strong>Contents of the Call</strong></summary>

As usual, Nick takes us through some new functionality from the Dev Team starting with showing off some new webhook functionality in the form of a Rewsty Bot that you can ask questions to.

Next we hear from Jareth on the power of Rewst outside of just MSP applications as he takes us through his workflow that uses public APIs to check for Steam deals. After that Tim shows off a great example of templates.

After that we hear from Mendy at Rising Tide Consulting Group on how he's used HTML templates and Rewst forms to embed our forms into Halo PSA's customer facing portal. Finally, we answer a number of your questions!

See you next week!

</details>

<details>

<summary><strong>How to get help from the ROC</strong></summary>

How to get help - Engage the ROC in Slack - Email support coming soon! - \[FUTURE] Live chat in the app - Would this be helpful to people? - Documentation - <https://rewst.help> - Feature 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/2023-roc-open-mics/march-3rd-2023-new-webhooks-tracking-steam-deals-and-templates-oh-my.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.