> 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/development-updates/2025-dev-updates/october-17-2025-dev-update.md).

# October 17, 2025 - Dev update

Explore what new changes the Dev team has deployed in the last week!

This can be anything from new features, bug fixes, or QoL changes!

<details>

<summary><strong>New features and items</strong></summary>

* **Integrations**
  * [1Stream (BVoiP) integration](/documentation/integrations/integration-guides/1stream-integration.md)
* **Workflows**
  * Enhanced RoboRewsty workflow notes with absolute positioning and styling options
* **App Builder**
  * Reduced front end bundle size to improve performance

</details>

<details>

<summary><strong>Bug fixes and chores</strong></summary>

* **Integrations**
  * Fixed sort in array sorting for Notion integration actions
  * Fixed an issue where default values in object action parameters weren’t being applied correctly.
* **Workflows**
  * Fixed an issue that caused certain workflow data to error when saving when using non-string keys. This improves reliability when handling complex data structures.

</details>

<details>

<summary><strong>Coming Soon</strong></summary>

* Custom OAuth app configuration for HubSpot integration
* Cloudmore integration

</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/development-updates/2025-dev-updates/october-17-2025-dev-update.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.